[Bug c/106920] -Warray-bound false positive regression with -O2 or -Os and constant address

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106920 --- Comment #5 from Dominique Martinet --- hmm this is a pretty complex topic. My problem like pointed out in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99578 is more with all the legacy code that I have to deal with, that isn't maintained

[Bug c/106920] -Warray-bound false positive regression with -O2 or -Os and constant address

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106920 --- Comment #2 from Dominique Martinet --- Thanks for the very fast reply! since you mentioned null pointers I now see this warning doesn't happen if I try with a larger constant, I just had bad luck that imx-atf uses an address < 4k...? I

[Bug c/106920] New: -Warray-bound false positive regression with -O2 or -Os

Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: npfhrotynz-ptnqh.myvf at noclue dot notk.org Target Milestone: --- Hello, I think I've run into a false positive on this file: https://source.codeaurora.org/external/imx/imx-atf/tree/plat/imx

[Bug analyzer/103217] analyzer false positive on leak warning when using indirect strdup

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103217 --- Comment #10 from Dominique Martinet --- Thank you for this work! I can confirm this indeed fixed the warning in my application as well, time to add a fanalyzer build to my CI :)

[Bug analyzer/103217] analyzer false positive on leak warning when using indirect strdup

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103217 --- Comment #5 from Dominique Martinet --- Ah, this apparently needed the unused fields in the struct, and the extra config_init() call. Here's something trimmed down from the actual program instead of building back up: - #define

[Bug analyzer/103217] analyzer false positive on leak warning when using indirect strdup

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103217 Dominique Martinet changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED

[Bug analyzer/99269] False positive -Wanalyzer-malloc-leak/-Wanalyzer-double-free with -fanalyzer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99269 Dominique Martinet changed: What|Removed |Added CC||npfhrotynz-ptnqh.myvf@noclu

[Bug analyzer/103217] New: analyzer false positive on leak warning when using indirect strdup

Priority: P3 Component: analyzer Assignee: dmalcolm at gcc dot gnu.org Reporter: npfhrotynz-ptnqh.myvf at noclue dot notk.org Target Milestone: --- Inlining both the reproducer and fanalyzer warning as they are small enough: -- #include #include

[Bug regression/94436] incompatible-pointer-types warning with container_of

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94436 Dominique Martinet changed: What|Removed |Added Resolution|--- |FIXED

[Bug regression/94436] New: incompatible-pointer-types warning with container_of

Component: regression Assignee: unassigned at gcc dot gnu.org Reporter: npfhrotynz-ptnqh.myvf at noclue dot notk.org Target Milestone: --- Created attachment 48157 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48157=edit test program.c This looks like a regression in warni

[Bug analyzer/94365] New: false positive leak when using container_of-like constructs

Priority: P3 Component: analyzer Assignee: dmalcolm at gcc dot gnu.org Reporter: npfhrotynz-ptnqh.myvf at noclue dot notk.org Target Milestone: --- Created attachment 48136 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48136=edit test program.c First, tha