From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-492941-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 57331 invoked by alias); 21 Jul 2015 17:10:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 57260 invoked by uid 48); 21 Jul 2015 17:10:48 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/66468] [6 Regression] ICE in in check_die, at dwarf2out.c:5719
Date: Tue, 21 Jul 2015 17:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: aldyh at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66468-4-NzMmO2W8Ky@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66468-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66468-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-07/txt/msg01831.txt.bz2

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

--- Comment #10 from Jason Merrill <jason at gcc dot gnu.org> ---
(In reply to Aldy Hernandez from comment #9)
> Do you think perhaps we could diagnose this sort of problem earlier so 
> it doesn't show up (confusingly) in dwarf2out land?

I'm not sure where to check that outside dwarf2out.

I tried adding

  gcc_checking_assert (cgraph_function_possibly_inlined_p (decl));

in gen_inlined_subroutine_die to make the problem clearer, and I get a bunch of
new failures in the debug tests, so it doesn't seem to be limited to LTO.