[Bug middle-end/51323] g++ confuses this with function argument in optimized call

dak at gnu dot org gcc-bugzilla@gcc.gnu.org
Mon Nov 28 20:13:00 GMT 2011


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51323

--- Comment #5 from David Kastrup <dak at gnu dot org> 2011-11-28 19:33:26 UTC ---
Question: the proposed fix is in gcc/calls.c which looks somewhat architecture
independent.  Am I right in assuming that this means that the bug may manifest
itself under architectures different from i686 given different conditions?

In that case, I would tend to just unconditionally do
-fno-optimize-sibling-calls in our autoconf checks for all respective gcc
versions independent from tests and architecture since I don't have the
hardware for other platforms in order to figure out compiler bugs, and since
the bug tends to hide its cause in the resulting segfault, as it occurs only
with tail jumps, meaning that the responsible function is not even visible in
the stack traceback.



More information about the Gcc-bugs mailing list