https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109364
--- Comment #10 from contact at thunderperfectwitchcraft dot org ---
Now I get it, thanks to you both.
Why not additionally make the -Werror=return-type option to default? Would make
it easier to detect and solve the issue, compared to a crashing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109364
--- Comment #7 from contact at thunderperfectwitchcraft dot org ---
I'm not sure if I understand you correct (as I'm not a native speaker): You say
that it crashes by chance because it is undefined behavior, right?
On reddit, I got this as a rep
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109364
--- Comment #5 from contact at thunderperfectwitchcraft dot org ---
As mentioned, it isn't anymore: According to the linked Thread in gcc 13 a
return value that contains a invalid instruction is generated on purpose if
there is no return statemen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109364
--- Comment #3 from contact at thunderperfectwitchcraft dot org ---
I'm not sure if you read the thread I linked: If the statements there are
correct, atm a instruction that causes a crash under any circumstances is
generated and returned if the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109364
Bug ID: 109364
Summary: Missing return statement in a non void function gives
only a warning but produces a forced crash.
Product: gcc
Version: 13.0
URL: https://www.
