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/45454] New: [4.6 Regression] ICE: in verify_target_availability, at sel-sched.c:1614 Date: Mon, 30 Aug 2010 19:39:00 -0000 [thread overview] Message-ID: <bug-45454-14164@http.gcc.gnu.org/bugzilla/> (raw) Command line: $ gcc -O1 -fvar-tracking-assignments -fcse-follow-jumps -frerun-cse-after-loop -fschedule-insns2 -fselective-scheduling2 -funroll-all-loops testcase.c Compiler output: $ gcc -O1 -fvar-tracking-assignments -fcse-follow-jumps -frerun-cse-after-loop -fschedule-insns2 -fselective-scheduling2 -funroll-all-loops testcase.c testcase.c:1:0: warning: var-tracking-assignments changes selective scheduling [enabled by default] testcase.c: In function 'foo': testcase.c:7:1: internal compiler error: in verify_target_availability, at sel-sched.c:1614 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. Tested revisions: r163636 - crash r162940 - crash r161659 - OK -- Summary: [4.6 Regression] ICE: in verify_target_availability, at sel-sched.c:1614 Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: zsojka at seznam dot cz GCC host triplet: x86_64-pc-linux-gnu GCC target triplet: x86_64-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45454
next reply other threads:[~2010-08-30 19:39 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-08-30 19:39 zsojka at seznam dot cz [this message] 2010-08-30 19:41 ` [Bug rtl-optimization/45454] " zsojka at seznam dot cz 2010-08-31 9:55 ` rguenth at gcc dot gnu dot org 2010-09-02 10:48 ` jakub at gcc dot gnu dot org 2010-09-02 11:00 ` zsojka at seznam dot cz 2010-09-05 20:44 ` aoliva 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-45454-14164@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).