[Bug c/47781] warnings from custom printf format specifiers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47781 Luke Shumaker changed: What|Removed |Added CC||lukeshu at lukeshu dot com --- Comment

[Bug target/119188] Incorrect -fcallgraph-info=su for leaf functions on x86-64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119188 --- Comment #2 from Luke Shumaker --- I appreciate the explanation. Does that make it any less of a bug? Should I change the title to "x86 red-zone not taken into account by -fcallgraph-info=su"?

[Bug c/119188] New: Incorrect -fcallgraph-info=su for leaf functions on x86-64

Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: lukeshu at lukeshu dot com Target Milestone: --- With the given simple strnlen function, I'm seeing -fcallgraph-info report that the function uses 16 bytes of stack space, but by my coun

[Bug tree-optimization/118814] [13/14/15 regression] -Warray-bounds causes internal compiler error: Segmentation fault during GIMPLE pass: vrp

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118814 --- Comment #4 from Luke Shumaker --- This had the keyword `ice-on-valid-code` (added by Sam James); bug 109828 has the keyword `ice-on-invalid-code`. I could be mistaken, but I believe that the code here is valid (and that GCC 12 was erroneous

[Bug c/118814] New: -Warray-bounds causes internal compiler error: Segmentation fault during GIMPLE pass: vrp

Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: lukeshu at lukeshu dot com Target Milestone: --- System / GCC version / GCC options: $ /usr/bin/gcc -v Using built-in specs. COLLECT_GCC=/bin/gcc

[Bug c/118212] New: False positive -Wstringop-truncation despite [[gnu::nonstring]]

Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: lukeshu at lukeshu dot com Target Milestone: --- System / GCC version / GCC options: $ gcc -v Using built-in specs. COLLECT_GCC=/usr/bin/gcc COLLECT_LTO_WRAPPER=/usr/lib

[Bug c/117469] returns_twice on defined functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117469 --- Comment #5 from Luke Shumaker --- Indeed. My mistake.

[Bug c/117469] returns_twice on defined functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117469 Luke Shumaker changed: What|Removed |Added CC||lukeshu at lukeshu dot com --- Comment

[Bug c/85957] i686: Integers appear to be different, but compare as equal

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85957 Luke Shumaker changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE

[Bug c/85957] New: i686: Integers appear to be different, but compare as equal

Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: lukeshu at lukeshu dot com Target Milestone: --- Created attachment 44200 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44200&action=edit The preprocessed source This is a bug