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/48374] New: ICE: in single_succ_edge, at basic-block.h:562 with -fselective-scheduling2 and __builtin_unreachable() Date: Wed, 30 Mar 2011 21:15:00 -0000 [thread overview] Message-ID: <bug-48374-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48374 Summary: ICE: in single_succ_edge, at basic-block.h:562 with -fselective-scheduling2 and __builtin_unreachable() 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 23824 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23824 reduced testcase Compiler output: $ gcc -O -fschedule-insns2 -fsel-sched-pipelining -fsel-sched-pipelining-outer-loops -fselective-scheduling2 --param max-sched-extend-regions-iters=100 testcase.c testcase.c: In function 'foo': testcase.c:14:1: internal compiler error: in single_succ_edge, at basic-block.h:562 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. Tested revisions: r171735 - crash 4.6 r171597 - crash 4.5 r171597 - crash 4.4 r171597 - doesn't know __builtin_unreachable
next reply other threads:[~2011-03-30 20:55 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-30 21:15 zsojka at seznam dot cz [this message] 2011-04-07 7:46 ` [Bug rtl-optimization/48374] " abel at gcc dot gnu.org 2011-05-10 18:35 ` zsojka at seznam dot cz 2012-01-25 13:33 ` abel at gcc dot gnu.org 2012-02-05 17:52 ` mikpe at it dot uu.se 2012-02-06 8:32 ` abel at gcc dot gnu.org 2012-10-30 8:26 ` abel at gcc dot gnu.org 2012-10-30 8:26 ` 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-48374-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: linkBe 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).