[Bug tree-optimization/108051] Missing array-bounds warning when not using -ftracer flag

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108051 Leandro Nini changed: What|Removed |Added CC||drfiemost at email dot it --- Comment #1

[Bug c/108051] New: Missing array-bounds warning when not using -ftracer flag

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108051 Bug ID: 108051 Summary: Missing array-bounds warning when not using -ftracer flag Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal P

[Bug middle-end/106776] Unexpected use-after-free warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106776 --- Comment #2 from Leandro Nini --- Oh, now I see it, it wasn't that obvious in the first test. But why is the compiler allowed to postpone the store after deleting the pointer? Is there some undefined behavior involved here or what?

[Bug middle-end/106776] New: Unexpected use-after-free warning

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106776 Bug ID: 106776 Summary: Unexpected use-after-free warning Product: gcc Version: 12.2.0 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3

[Bug tree-optimization/98444] New: [10 Regression] compile error with -ftracer and -Werror=format-overflow

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98444 Bug ID: 98444 Summary: [10 Regression] compile error with -ftracer and -Werror=format-overflow Product: gcc Version: 10.2.1 URL: https://github.com/elogind/elogind/iss