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 tree-optimization/48330] New: [4.7 Regression] ICE: in optimize_inline_calls, at tree-inline.c:4201 with -fmudflap -fno-early-inlining
Date: Tue, 29 Mar 2011 10:57:00 -0000	[thread overview]
Message-ID: <bug-48330-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: [4.7 Regression] ICE: in optimize_inline_calls, at
                    tree-inline.c:4201 with -fmudflap -fno-early-inlining
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: zsojka@seznam.cz
                CC: jamborm@gcc.gnu.org
              Host: x86_64-pc-linux-gnu
            Target: x86_64-pc-linux-gnu


It seems any input file is enough to trigger the assertion.

Compiler output:
$ echo '' > testcase.c
$ gcc -O -fmudflap -fno-early-inlining testcase.c 
testcase.c: In function '_GLOBAL__sub_I_00099_0_testcase.c':
testcase.c:1:0: internal compiler error: in optimize_inline_calls, at
tree-inline.c:4201
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

That assert was added in
http://gcc.gnu.org/viewcvs?view=revision&revision=171602


             reply	other threads:[~2011-03-29 10:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29 10:57 zsojka at seznam dot cz [this message]
2011-03-29 13:13 ` [Bug tree-optimization/48330] " jamborm at gcc dot gnu.org
2011-03-29 13:27 ` jamborm at gcc dot gnu.org
2011-04-06  0:25 ` pinskia at gcc dot gnu.org
2011-04-18 14:36 ` jamborm 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-48330-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).