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/94461] [10 Regression] ICE: in extract_insn, at recog.c:2294 with __builtin_ia32_pmuludq() and -mno-sse2
Date: Thu, 02 Apr 2020 18:12:30 +0000	[thread overview]
Message-ID: <bug-94461-4-rT8AlVaq8b@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94461-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94461

--- Comment #1 from Zdenek Sojka <zsojka at seznam dot cz> ---
This seems to affect sse3 intrinsics as well:
$ gcc-10 testcase-min0.i -w
testcase-min0.i: In function 'foo0':
testcase-min0.i:15:1: error: unrecognizable insn:
   15 | }
      | ^
(insn 28 27 29 2 (set (reg:V2SI 83 [ _2 ])
        (vec_concat:V2SI (minus:SI (vec_select:SI (reg:V2SI 95)
                    (parallel [
                            (const_int 0 [0])
                        ]))
                (vec_select:SI (reg:V2SI 95)
                    (parallel [
                            (const_int 1 [0x1])
                        ])))
            (minus:SI (vec_select:SI (reg:V2SI 82 [ _1 ])
                    (parallel [
                            (const_int 0 [0])
                        ]))
                (vec_select:SI (reg:V2SI 82 [ _1 ])
                    (parallel [
                            (const_int 1 [0x1])
                        ]))))) "testcase-min0.i":14:20 -1
     (nil))
during RTL pass: vregs
testcase-min0.i:15:1: internal compiler error: in extract_insn, at recog.c:2294
0x6d36a8 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
        /repo/gcc-trunk/gcc/rtl-error.c:108
0x6d372b _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
        /repo/gcc-trunk/gcc/rtl-error.c:116
0x6c2b11 extract_insn(rtx_insn*)
        /repo/gcc-trunk/gcc/recog.c:2294
0xca6a83 instantiate_virtual_regs_in_insn
        /repo/gcc-trunk/gcc/function.c:1607
0xca6a83 instantiate_virtual_regs
        /repo/gcc-trunk/gcc/function.c:1977
0xca6a83 execute
        /repo/gcc-trunk/gcc/function.c:2026
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

$ gcc-9 testcase-min0.i -w
testcase-min0.i: In function 'foo0':
testcase-min0.i:14:20: error: '__builtin_ia32_phsubd' needs isa option -mssse3
-mmmx
   14 |  v64s32 v64s32_3 = __builtin_ia32_psrld(__builtin_ia32_phsubd
(v64s32_2, __builtin_ia32_pandn(v64s32_1, v64s32_2)), v64s32_0);
      |                   
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Applies at least to __builtin_ia32_psubd() and __builtin_ia32_psubb() as well.

  reply	other threads:[~2020-04-02 18:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-02 17:58 [Bug target/94461] New: " zsojka at seznam dot cz
2020-04-02 18:12 ` zsojka at seznam dot cz [this message]
2020-04-02 18:52 ` [Bug target/94461] " jakub at gcc dot gnu.org
2020-04-03  7:06 ` rguenth at gcc dot gnu.org
2020-04-03  7:49 ` ubizjak at gmail dot com
2020-04-03 11:01 ` hjl.tools at gmail dot com
2020-04-03 11:04 ` hjl.tools at gmail dot com
2020-04-03 11:05 ` hjl.tools at gmail dot com
2020-04-03 11:26 ` jakub at gcc dot gnu.org
2020-04-03 12:26 ` jakub at gcc dot gnu.org
2020-04-03 12:41 ` hjl.tools at gmail dot com
2020-04-03 12:51 ` jakub at gcc dot gnu.org
2020-04-03 12:57 ` jakub at gcc dot gnu.org
2020-04-03 13:52 ` hjl.tools at gmail dot com
2020-04-03 13:57 ` jakub at gcc dot gnu.org
2020-04-03 14:10 ` jakub at gcc dot gnu.org
2020-04-03 18:34 ` cvs-commit at gcc dot gnu.org
2020-04-03 18:35 ` 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-94461-4-rT8AlVaq8b@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: link
Be 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).