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 target/47975] New: ICE: in expand_shift, at expmed.c:2299 when using 256b vectors without -mavx Date: Thu, 03 Mar 2011 15:30:00 -0000 [thread overview] Message-ID: <bug-47975-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47975 Summary: ICE: in expand_shift, at expmed.c:2299 when using 256b vectors without -mavx Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target AssignedTo: unassigned@gcc.gnu.org ReportedBy: zsojka@seznam.cz Host: x86_64-pc-linux-gnu Target: x86_64-pc-linux-gnu Created attachment 23533 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23533 reduced testcase $ gcc testcase.c testcase.c: In function 'foo': testcase.c:6:5: internal compiler error: in expand_shift, at expmed.c:2299 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. $ gcc-4.5.2 testcase.c testcase.c: In function 'foo': testcase.c:6:5: error: invalid operands to binary << (have '__vector(8) int' and '__vector(8) int') Tested revisions: r170622 - crash 4.5 - code is rejected
next reply other threads:[~2011-03-03 15:30 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-03 15:30 zsojka at seznam dot cz [this message] 2011-03-03 16:01 ` [Bug target/47975] " rguenth at gcc dot gnu.org 2011-03-03 16:19 ` rguenth at gcc dot gnu.org 2011-03-03 16:22 ` rguenth at gcc dot gnu.org 2011-03-04 10:27 ` rguenth at gcc dot gnu.org 2011-03-04 10:28 ` rguenth 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-47975-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).