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/43056] New: __builtin_prefetch causes ICE: in rtl_verify_flow_info, at cfgrtl.c:2205 with -fsched2-use-superblocks Date: Sat, 13 Feb 2010 13:00:00 -0000 [thread overview] Message-ID: <bug-43056-14164@http.gcc.gnu.org/bugzilla/> (raw) Command line: gcc -O1 -fschedule-insns2 -fsched2-use-superblocks -c testcase.c -------- testcase.c -------- int x[1]; void foo() { __builtin_prefetch(x); } ---------------------------- Tested revisions: trunk r156745 - crash trunk r153685 - crash 4.4 r156256 - crash 4.4 r155365 - OK (no checking) 4.4 r149995 - crash Output: $ /mnt/svn/gcc-trunk/binary-156745-lto/bin/gcc -O1 -fschedule-insns2 -fsched2-use-superblocks -c testcase.c testcase.c: In function ‘foo’: testcase.c:5:1: error: missing barrier after block 2 testcase.c:5:1: error: return not followed by barrier (jump_insn:TI 11 14 8 2 testcase.c:5 (return) 648 {return_internal} (nil)) testcase.c:5:1: internal compiler error: in rtl_verify_flow_info, at cfgrtl.c:2205 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. -- Summary: __builtin_prefetch causes ICE: in rtl_verify_flow_info, at cfgrtl.c:2205 with -fsched2-use-superblocks Product: gcc Version: 4.4.4 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=43056
next reply other threads:[~2010-02-13 13:00 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-02-13 13:00 zsojka at seznam dot cz [this message] 2010-02-13 23:09 ` [Bug rtl-optimization/43056] " steven at gcc dot gnu dot org 2010-02-13 23:18 ` steven at gcc dot gnu dot org 2010-02-13 23:29 ` steven at gcc dot gnu dot org 2010-02-14 0:08 ` steven 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-43056-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).