[Bug c/105950] > O2 optimization causes runtime (SIGILL) during main initialization

jkanapes at yahoo dot com gcc-bugzilla@gcc.gnu.org
Tue Jun 14 09:27:01 GMT 2022


--- Comment #11 from John Kanapes <jkanapes at yahoo dot com> ---
(In reply to Richard Biener from comment #9)
> Note that GCC 9 is no longer supported.  Note one common error resulting in
> SIGILL is when you fall through to an unreachable place which could be
> padding
> (like when there's a missing return in a function).

gcc 9.40 is the distro gcc for Ubuntu 20.04, which is LTS and still supported.
Does this mean that no action will be taken upon resolving this ticket?
I am trying to recreate this bug in a smaller, more concise context.
It is not an obvious bug. This is valid code, and it takes a large chain of
previous steps to get it wrong at runtime. It used to work with previous gccs,
but it now seems broken:(
It will remain broken in future releases unless we stop it here:(
I hope you reconsider:)
If that was a problem of a missing return in a function, it would have to be an
internal function. The spot it happens is in main initialization, before it had
a chance to call any of my functions.

More information about the Gcc-bugs mailing list