[Bug analyzer/114677] New: apparent -Wanalyzer-fd-leak false positive

: analyzer Assignee: dmalcolm at gcc dot gnu.org Reporter: levon at movementarian dot org Target Milestone: --- Created attachment 57920 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57920&action=edit reproducer https://godbolt.org/z/PfKKbPhdP reproduced with

[Bug tree-optimization/88867] -Waggressive-loop-optimizations doesn't warn when -faggressive-loop-optimizations is in play

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88867 --- Comment #2 from John Levon --- There is no Address Sanitizer in our kernel, bootloaders etc.

[Bug c/88867] New: -Waggressive-loop-optimizations doesn't warn when -faggressive-loop-optimizations is in play

IRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: levon at movementarian dot org Target Milestone: --- Given how dangerous -faggressive-loop-optimizations has been proven to be, it's unfort

[Bug middle-end/35587] -Warray-bounds does not work at all or does not find all trivial cases, and :works only with -O2 or -O3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35587 --- Comment #11 from John Levon --- Ugh, and in fact, the sanitize option isn't even enough for the real-life code that we hit this with.

[Bug middle-end/35587] -Warray-bounds does not work at all or does not find all trivial cases, and :works only with -O2 or -O3

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35587 John Levon changed: What|Removed |Added CC||levon at movementarian dot org --- Comment

[Bug c/7543] no warning for always-false "if (!a & 0x4)" bitwise and on boolean value

--- Comment #12 from levon at movementarian dot org 2007-01-21 03:15 --- It's been a cause of bugs time and time again, so yes, it's useful and important. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7543