public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dwmw2 at infradead dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/28779]  New: internal compiler error: in cgraph_estimate_size_after_inlining, at ipa-inline.c:106
Date: Sat, 19 Aug 2006 09:25:00 -0000	[thread overview]
Message-ID: <bug-28779-9416@http.gcc.gnu.org/bugzilla/> (raw)

See attached test case (ignore the warning; cf. pr27899):
/opt/crosstool/gcc-4.1.0-glibc-2.3.6/i686-unknown-linux-gnu/bin/i686-unknown-linux-gnu-gcc-4.1.0
-c -o e1000.o e1000_hw.i e1000_main.i --combine -fwhole-program -Os
In file included from /pmac/git/geode/include/linux/thread_info.h:22,
                 from /pmac/git/geode/include/linux/preempt.h:10,
                 from /pmac/git/geode/include/linux/spinlock.h:50,
                 from /pmac/git/geode/include/linux/capability.h:46,
                 from /pmac/git/geode/include/linux/sched.h:45,
                 from /pmac/git/geode/include/linux/module.h:10,
                 from /pmac/git/geode/drivers/net/e1000/e1000.h:38,
                 from /pmac/git/geode/drivers/net/e1000/e1000_main.c:31:
include2/asm/thread_info.h:88: warning: register used for two global register
variables
/pmac/git/geode/drivers/net/e1000/e1000_main.c:4860: internal compiler error:
in cgraph_estimate_size_after_inlining, at ipa-inline.c:106
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.

Seen with 4.1.0 i386 (with the set of patches at
http://david.woodhou.se/combine/gcc-patches since otherwise it dies a lot
earlier) and also with Red Hat's 4.1.1 branch with same patches, for i386 and
PowerPC. The attached preprocessed source will be i386.

Sorry, I'm not sure how to cut the test case down to something smaller.


-- 
           Summary: internal compiler error: in
                    cgraph_estimate_size_after_inlining, at ipa-inline.c:106
           Product: gcc
           Version: 3.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dwmw2 at infradead dot org


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


             reply	other threads:[~2006-08-19  9:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-19  9:25 dwmw2 at infradead dot org [this message]
2006-08-19  9:26 ` [Bug c/28779] " dwmw2 at infradead dot org
2006-08-19  9:29 ` dwmw2 at infradead dot org
2006-08-19 15:40 ` [Bug middle-end/28779] " rguenth at gcc dot gnu dot org
2006-08-19 15:53 ` dwmw2 at infradead dot org
2006-08-19 16:35 ` rguenth at gcc dot gnu dot org
2006-08-19 17:16 ` rguenth at gcc dot gnu dot org
2006-08-19 21:25 ` hubicka at gcc dot gnu dot org
2006-08-20 18:47 ` hubicka at gcc dot gnu dot org
2008-01-11  9:43 ` steven at gcc dot gnu dot org
2008-01-11 13:59 ` aldot at gcc dot gnu dot org
2008-01-11 14:22 ` hubicka at ucw dot cz
2008-01-11 15:57 ` aldot at gcc dot gnu dot org
2008-02-17 20:33 ` hubicka at gcc dot gnu dot org
2008-02-19 17:11 ` hubicka at gcc dot gnu dot org
2008-07-16 12:49 ` aldot at gcc dot gnu dot org
2008-08-27 22:03 ` jsm28 at gcc dot gnu dot org
2009-01-24 10:20 ` rguenth at gcc dot gnu dot org
2009-03-10 13:57 ` rguenth at gcc dot gnu dot 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-28779-9416@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).