https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105654
Max Ferger <max.ferger at gmx dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |max.ferger at gmx dot de
--- Comment #5 from Max Ferger <max.ferger at gmx dot de> ---
Created attachment 59596
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59596&action=edit
Minimal self-contained test
I've condensed the code that is supposedly misunderstood by the compiler down
into a self-contained test that can produce a binary.
The wrong code will lead to SIGSEGV while running the binary.
With good code, the binary terminates with an exit value of 32;
or would terminate with exit 0, if `some_value` were 0.
I think this helps in coming up with a unit-test against the reported behavior.
You can see this in live action: https://godbolt.org/z/f6q5sWx1E
