public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/47975] ICE: in expand_shift, at expmed.c:2299 when using 256b vectors without -mavx Date: Thu, 03 Mar 2011 16:19:00 -0000 [thread overview] Message-ID: <bug-47975-4-9GBDJh6xW4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47975-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47975 --- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-03-03 16:19:23 UTC --- We lower the vector - vector shift to <bb 2>: x.0_1 = x; x.1_2 = x; D.2689_4 = BIT_FIELD_REF <x.0_1, 128, 0>; D.2690_5 = BIT_FIELD_REF <x.1_2, 128, 0>; D.2691_6 = D.2689_4 << D.2690_5; D.2692_7 = BIT_FIELD_REF <x.0_1, 128, 128>; D.2693_8 = BIT_FIELD_REF <x.1_2, 128, 128>; D.2694_9 = D.2692_7 << D.2693_8; x.2_3 = {D.2691_6, D.2694_9}; x = x.2_3; return; but do not lower that shift further because type_for_widest_vector_mode calls optab_handler with ashl_optab which happens because in optab_for_tree_code we have case LSHIFT_EXPR: if (VECTOR_MODE_P (TYPE_MODE (type))) { if (subtype == optab_vector) return TYPE_SATURATING (type) ? NULL : vashl_optab; gcc_assert (subtype == optab_scalar); } if (TYPE_SATURATING(type)) return TYPE_UNSIGNED(type) ? usashl_optab : ssashl_optab; return ashl_optab; and we have ... #define TYPE_MODE(NODE) \ (TREE_CODE (TYPE_CHECK (NODE)) == VECTOR_TYPE \ ? vector_type_mode (NODE) : (NODE)->type.mode) which returns BLKmode instead of V8SImode. Bah to whoever introduced that hack to TYPE_MODE.
next prev parent reply other threads:[~2011-03-03 16:19 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-03 15:30 [Bug target/47975] New: " zsojka at seznam dot cz 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 [this message] 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-9GBDJh6xW4@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).