[Bug bootstrap/83396] [8 Regression] Bootstrap failures with Statement Frontiers

jakub at gcc dot gnu.org gcc-bugzilla@gcc.gnu.org
Wed Dec 13 16:09:00 GMT 2017


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83396

--- Comment #39 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to David Edelsohn from comment #37)
> Jakub, the -fcompare-debug failure is not new.  The root cause has been
> analyzed before. AIX specifically does not want to push unnecessary stack
> frames for code that is not compiled with debugging solely for matching code
> generation.

The question is, is it really needed for proper debugging even after 12 years
since it has been checked last (and even in that case it doesn't look like it
has been verified it doesn't work)?  And, if it is needed for XCOFF_DEBUG, is
it also needed for DWARF2_DEBUG?  I mean, at least the dwarf case in theory
should have all means to represent automatic variables in the frame regardless
of it, and gdb must handle it too.  What other debuggers you use on aix for
-gdwarf-* debugging?


More information about the Gcc-bugs mailing list