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 rtl-optimization/48144] New: ICE: in code_motion_path_driver, at sel-sched.c:6575 with -fselective-scheduling2 and custom flags
Date: Wed, 16 Mar 2011 02:53:00 -0000	[thread overview]
Message-ID: <bug-48144-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: ICE: in code_motion_path_driver, at sel-sched.c:6575
                    with -fselective-scheduling2 and custom flags
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: rtl-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: zsojka@seznam.cz
              Host: x86_64-pc-linux-gnu
            Target: x86_64-pc-linux-gnu


Created attachment 23676
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23676
auto-reduced testcase (from gfortran.dg/intrinsic_ifunction_1.f90)

I am sorry for the insane flags needed to reproduce, but I hope this uncovers
some possibly hidden problem.

Compiler output:
$ gfortran -O -fira-region=one -fno-dce -fno-guess-branch-probability
-fno-ivopts -frerun-cse-after-loop -fschedule-insns2 -fsel-sched-pipelining
-fsel-sched-pipelining-outer-loops -fselective-scheduling2 -fno-tree-copyrename
-funroll-loops --param=max-cse-insns=50 --param=max-pipeline-region-blocks=30
testcase.f90 
testcase.f90: In function 'gf0026':
testcase.f90:6:0: internal compiler error: in code_motion_path_driver, at
sel-sched.c:6575
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.


             reply	other threads:[~2011-03-16  2:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16  2:53 zsojka at seznam dot cz [this message]
2011-03-16  8:36 ` [Bug rtl-optimization/48144] " abel at gcc dot gnu.org
2011-03-20 18:53 ` zsojka at seznam dot cz
2011-03-22 16:29 ` abel at gcc dot gnu.org
2011-03-22 20:19 ` zsojka at seznam dot cz
2011-03-26 12:35 ` abel at gcc dot gnu.org
2011-04-07  7:05 ` abel at gcc dot gnu.org
2011-04-07 12:07 ` abel at gcc dot gnu.org
2011-04-07 12:07 ` abel 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-48144-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).