[Bug analyzer/99854] gcc 11 snapshot 20210328: "lto1: fatal error: Cgraph edge statement index out of range" when building Valgrind with LTO and -fanalyzer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99854 jseward at acm dot org changed: What|Removed |Added Resolution|DUPLICATE |FIXED --- Comment #2 from jsewar

[Bug analyzer/99854] New: gcc 11 snapshot 20210328: "lto1: fatal error: Cgraph edge statement index out of range" when building Valgrind with LTO and -fanalyzer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99854 Bug ID: 99854 Summary: gcc 11 snapshot 20210328: "lto1: fatal error: Cgraph edge statement index out of range" when building Valgrind with LTO and -fanalyzer Product: gcc

[Bug rtl-optimization/98692] Unitialized Values reported only with -Os

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98692 --- Comment #22 from jseward at acm dot org --- Looking back at the above, it's now clearer what the problem is: # Park potentially live data in the red zone _savegpr0_14: std r14,-144(r1) _savegpr0_15: std r15,-136(r1) _savegpr0_16:

[Bug rtl-optimization/98692] Unitialized Values reported only with -Os

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98692 --- Comment #21 from jseward at acm dot org --- (In reply to Jakub Jelinek from comment #20) > Can you disable it just for these magic entrypoints (either by name or by > content)? In principle yes. I prefer by-content rather than by-name, in th

[Bug rtl-optimization/98692] Unitialized Values reported only with -Os

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98692 jseward at acm dot org changed: What|Removed |Added CC||jseward at acm dot org --- Comme