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/46522] New: ICE: in reset_sched_cycles_in_current_ebb, at sel-sched.c:7092 with -O3 -fsel-sched-pipelining -fselective-scheduling2 -funroll-loops
Date: Wed, 17 Nov 2010 16:14:00 -0000 [thread overview]
Message-ID: <bug-46522-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46522
Summary: ICE: in reset_sched_cycles_in_current_ebb, at
sel-sched.c:7092 with -O3 -fsel-sched-pipelining
-fselective-scheduling2 -funroll-loops
Product: gcc
Version: 4.6.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 22432
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22432
reduced testcase (originally PR45352 comment #19)
I am sorry for the amount of compiler flags, removing any of them causes the
ICE to disappear. Even manual partial inlining, unrolling, loop unswitching,
... either removes the ICE or doesn't allow me to remove further flags.
Flags are either:
-O3 -fkeep-inline-functions -fsel-sched-pipelining -fselective-scheduling2
-funroll-loops
or
-O2 -fkeep-inline-functions -fsel-sched-pipelining -fselective-scheduling2
-funroll-loops -funswitch-loops
or
-O1 -fcse-follow-jumps -fkeep-inline-functions -fpartial-inlining
-freorder-blocks -frerun-cse-after-loop -fschedule-insns2
-fsel-sched-pipelining -fselective-scheduling2 -funroll-loops -funswitch-loops
Compiler output:
$ gcc -O3 -fkeep-inline-functions -fsel-sched-pipelining
-fselective-scheduling2 -funroll-loops pr46522.c
pr46522.c: In function 'foo2':
pr46522.c:30:1: internal compiler error: in reset_sched_cycles_in_current_ebb,
at sel-sched.c:7092
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
Tested revisions (for the -O1 case):
r166795 - crash
r165699 - OK
4.5 - doesn't know -fpartial-inlining
next reply other threads:[~2010-11-17 16:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 16:14 zsojka at seznam dot cz [this message]
2010-11-18 7:31 ` [Bug rtl-optimization/46522] " hjl.tools at gmail dot com
2010-11-18 14:29 ` abel at gcc dot gnu.org
2010-12-21 12:14 ` abel at gcc dot gnu.org
2010-12-22 7:47 ` abel at gcc dot gnu.org
2011-01-13 9:55 ` abel at gcc dot gnu.org
2011-04-07 7:04 ` 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-46522-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).