public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/58332] New: error: inlined_to pointer is set but no predecessors found
Date: Fri, 06 Sep 2013 09:54:00 -0000	[thread overview]
Message-ID: <bug-58332-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 58332
           Summary: error: inlined_to pointer is set but no predecessors
                    found
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: ipa
          Assignee: unassigned at gcc dot gnu.org
          Reporter: rsandifo at gcc dot gnu.org
                CC: hubicka at gcc dot gnu.org
            Target: x86_64-linux-gnu

The following testcase:

----------------------------------------------------------------------------
static inline int foo (int x) { return x + 1; }
__attribute__ ((__optimize__ (0))) int bar (void) { return foo (100); }
----------------------------------------------------------------------------

ICEs after r202187 with:

----------------------------------------------------------------------------
foo.c:2:71: error: inlined_to pointer is set but no predecessors found
 __attribute__ ((__optimize__ (0))) int bar (void) { return foo (100); }
                                                                       ^
_ZL3fooi/0 (int foo(int)) @0x7f6911eac000
  Type: function definition analyzed
  Visibility: prevailing_def_ironly
  References: 
  Referring: 
  Function int foo(int)/0 is inline copy in int bar()/1
  Availability: local
  Function flags: body local
  Called by: 
  Calls: 
/tmp/foo.c:2:71: internal compiler error: verify_cgraph_node failed
0x918f05 verify_cgraph_node(cgraph_node*)
        /home/richards/gcc/wide-int/gcc/gcc/cgraph.c:2866
0x910531 verify_symtab_node(symtab_node_def*)
        /home/richards/gcc/wide-int/gcc/gcc/symtab.c:772
0x910598 verify_symtab()
        /home/richards/gcc/wide-int/gcc/gcc/symtab.c:789
0x921389 compile()
        /home/richards/gcc/wide-int/gcc/gcc/cgraphunit.c:2146
0x9214b1 finalize_compilation_unit()
        /home/richards/gcc/wide-int/gcc/gcc/cgraphunit.c:2209
0x697554 cp_write_global_declarations()
        /home/richards/gcc/wide-int/gcc/gcc/cp/decl2.c:4364
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
----------------------------------------------------------------------------

I'm not saying we did the right thing before that either,
just that it didn't ICE :-)


             reply	other threads:[~2013-09-06  9:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-06  9:54 rsandifo at gcc dot gnu.org [this message]
2013-09-06 10:10 ` [Bug ipa/58332] " hubicka at gcc dot gnu.org
2013-09-17  4:33 ` mpolacek at gcc dot gnu.org
2013-09-17  7:51 ` [Bug ipa/58332] [4.9 Regression] " rguenth at gcc dot gnu.org
2013-09-17 18:40 ` hubicka at gcc dot gnu.org
2013-09-17 21:57 ` jan.smets@alcatel-lucent.com

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-58332-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).