public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/49411] [4.6/4.7] ICE: unrecognizable insn with -mxop in _mm_roti_epi8 with negative number Date: Tue, 14 Jun 2011 23:22:00 -0000 [thread overview] Message-ID: <bug-49411-4-og1WL0xaxP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49411-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49411 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-06-14 23:21:32 UTC --- It ICEs even for positive values such as _mm_roti_epi8 (s, 76); I think multi_arg builtin expansion needs to do constant argument checking, at least for IX86_BUILTIN_VPROT[BWDQ]_IMM and IX86_BUILTIN_VPERMIL2P[DS]{,256}. And for the former ones either use CODE_FOR_* of an expander that handles both positive and negative values, where for positive one it would expand to xop_rotl* and for negative to xop_rotr* with the shift count negated, or the negation and choice of pattern needs to be done in ix86_expand_multi_arg_builtin.
next prev parent reply other threads:[~2011-06-14 23:22 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-14 22:43 [Bug target/49411] New: " qneill at gcc dot gnu.org 2011-06-14 23:22 ` jakub at gcc dot gnu.org [this message] 2011-06-15 5:48 ` [Bug target/49411] " jakub at gcc dot gnu.org 2011-06-15 6:33 ` jakub at gcc dot gnu.org 2011-06-15 15:38 ` qneill at gcc dot gnu.org 2011-06-15 15:57 ` jakub at gcc dot gnu.org 2011-06-15 16:40 ` qneill at gcc dot gnu.org 2011-06-18 6:43 ` jakub at gcc dot gnu.org 2011-06-18 9:08 ` jakub at gcc dot gnu.org 2011-06-18 9:19 ` jakub 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-49411-4-og1WL0xaxP@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).