https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115777
Bug ID: 115777
Summary: Severe performance regression on insertion sort at -O2
or above
Product: gcc
Version: 14.1.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115590
--- Comment #3 from nrk at disroot dot org ---
> I am not 100% sure want to keep these around even at -O0 since they don't
> have any behavior effect.
I'd strongly argue that if you're using sanitizers, you'd want these to be
caught :)
Also wo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115590
Bug ID: 115590
Summary: Bad dereferences through -> operator not detected by
sanitizers
Product: gcc
Version: 14.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96503
nrk at disroot dot org changed:
What|Removed |Added
CC||nrk at disroot dot org
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111665
Bug ID: 111665
Summary: internal compiler error: in
c_objc_common_truthvalue_conversion
Product: gcc
Version: 13.2.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110676
--- Comment #3 from nrk at disroot dot org ---
Oops, forgot about https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107395.
But that bug was for missed warning opportunity, while this one is about ASan.
So I suppose both the bugs can coexist.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110676
Bug ID: 110676
Summary: builtin optimization prevents ASan from detecting OOB
reads
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107395
--- Comment #2 from nrk at disroot dot org ---
That c++ warning is unrelated to the bug report, it's warning about
initialization; which you can easily replace them with { 'h' } and { 'h', 'i' }
to silence; but not warning about the fact that non
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107395
Bug ID: 107395
Summary: Missed warning opportunity on bultin string
optimization
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106620
--- Comment #3 from nrk at disroot dot org ---
> Feel free to reopen it if you're able to reproduce it with gcc 12 or later
Huh, I linked to godbolt specifically because I wanted to test gcc 12 and see
if the bug still persists or not since my l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106620
Bug ID: 106620
Summary: Incorrectly thinks execution can continue after a
return statement
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104288
Bug ID: 104288
Summary: Null pointer check invalidly deleted
Product: gcc
Version: 11.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
12 matches
Mail list logo