This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/49411] [4.6/4.7] ICE: unrecognizable insn with -mxop in _mm_roti_epi8 with negative number
- From: "jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 15 Jun 2011 15:57:35 +0000
- Subject: [Bug target/49411] [4.6/4.7] ICE: unrecognizable insn with -mxop in _mm_roti_epi8 with negative number
- Auto-submitted: auto-generated
- References: <bug-49411-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49411
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-06-15 15:57:29 UTC ---
FYI, a newer patch has been posted:
http://gcc.gnu.org/ml/gcc-patches/2011-06/msg01139.html
I don't think it is necessary to test the op of vpermil again if it is
CONST_INT, we know it is not 0..3 because otherwise
insn_data[icode].operand[i + 1].predicate (op, mode)
would be true.
_mm_com* don't seem to have an constant argument, just two vector arguments, so
there is nothing to check. The immediate comes directly from the table and so
is known to be ok.