https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106578
--- Comment #4 from Gökçe Aydos ---
Just to clarify my entry:
In my opinion gcc should not fire a warning in my first example. In case
`realloc` was not successful, then `realloc` does not touch its argument. I
should be able to use its argumen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106578
--- Comment #3 from Gökçe Aydos ---
> using 'tmp' instead makes it properly fire.
Dear Richard, maybe I misunderstood what you meant with *fire*. If `tmp` is
used then gcc does not *fire* any warning and works correctly, right?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106578
--- Comment #1 from Gökçe Aydos ---
FYI: [`realloc` behavior in the C11
standard](http://port70.net/~nsz/c/c11/n1570.html#7.22.3.5)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106578
Bug ID: 106578
Summary: spurious -Wuse-after-free=2 after conditional free()
Product: gcc
Version: 12.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Comp
