public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/46132] New: ICE: in force_decl_die, at dwarf2out.c:20525 with -fenable-icf-debug
Date: Fri, 22 Oct 2010 14:49:00 -0000	[thread overview]
Message-ID: <bug-46132-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: ICE: in force_decl_die, at dwarf2out.c:20525 with
                    -fenable-icf-debug
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: debug
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: zsojka@seznam.cz


Created attachment 22123
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22123
reduced testcase

Compiler output:
$ gcc -O -g -fenable-icf-debug pr46132.c 
pr46132.c: In function 'regex_subst':
pr46132.c:5:1: internal compiler error: in force_decl_die, at dwarf2out.c:20525
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

Compiler output - 4.5:
$ gcc -O -g -fenable-icf-debug pr46132.c 
pr46132.c: In function 'foo':
pr46132.c:4:1: internal compiler error: tree check: expected tree that contains
'decl minimal' structure, have 'string_cst' in lookup_decl_die, at
dwarf2out.c:7701
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

Another issue with -fenable-icf-debug is PR44689

Tested revisions:
r165822 - crash
r153685 - crash
4.5 r165781 - crash


             reply	other threads:[~2010-10-22 14:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22 14:49 zsojka at seznam dot cz [this message]
2010-10-27 21:26 ` [Bug debug/46132] " pinskia at gcc dot gnu.org
2015-03-16  8:37 ` burnus at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-46132-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).