This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug debug/66688] [6 Regression] compare debug failure building Linux kernel on ppc64le
- From: "jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 14 Dec 2015 14:01:29 +0000
- Subject: [Bug debug/66688] [6 Regression] compare debug failure building Linux kernel on ppc64le
- Auto-submitted: auto-generated
- References: <bug-66688-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66688
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |ASSIGNED
Resolution|FIXED |---
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 37027
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=37027&action=edit
gcc6-pr66688.patch
I think this just went latent with those changes. The problem I see is that
cleanup_control_flow_bb can be called before fixup_noreturn_call is performed,
and in that case can either find a noreturn call at the end of bb if -g0 or
can't if the noreturn call is followed by some debug stmts. This hunk fixes
the case so that it is handled the same.