public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107863] [10/11/12/13 Regression] ICE with unrecognizable insn when using -funsigned-char with some SSE/AVX builtins Date: Thu, 24 Nov 2022 19:30:16 +0000 [thread overview] Message-ID: <bug-107863-4-6Fbi3iGb8X@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107863-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107863 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |10.5 Summary|ICE with unrecognizable |[10/11/12/13 Regression] |insn when using |ICE with unrecognizable |-funsigned-char with some |insn when using |AVX builtins |-funsigned-char with some | |SSE/AVX builtins Known to work| |4.4.7 Keywords| |ice-on-valid-code Known to fail| |4.5.3 Last reconfirmed| |2022-11-24 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Reduced to just: #include <immintrin.h> __m128i f(__m128i a) { return _mm_insert_epi8(a, -1, 2); } This only requires -msse4.1 -funsigned-char to reproduce the ICE. ;; _4 = __builtin_ia32_vec_set_v16qi (_1, 255, 2); (insn 7 6 8 (set (reg:QI 86) (const_int 255 [0xff])) "/app/example.cpp":4:11 -1 (nil)) Without -funsigned-char: ;; _4 = __builtin_ia32_vec_set_v16qi (_1, -1, 2); (insn 7 6 8 (set (reg:QI 86) (const_int -1 [0xffffffffffffffff])) "/app/example.cpp":4:11 -1 (nil)) I suspect the issue is the definition of __builtin_ia32_vec_set_v16qi uses char type rather than signed/unsigned char here ...
next prev parent reply other threads:[~2022-11-24 19:30 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-24 19:06 [Bug target/107863] New: ICE with unrecognizable insn when using -funsigned-char with some AVX builtins bouanto at zoho dot com 2022-11-24 19:30 ` pinskia at gcc dot gnu.org [this message] 2022-11-24 19:35 ` [Bug target/107863] [10/11/12/13 Regression] ICE with unrecognizable insn when using -funsigned-char with some SSE/AVX builtins pinskia at gcc dot gnu.org 2022-11-24 20:12 ` rguenth at gcc dot gnu.org 2022-11-25 2:26 ` crazylht at gmail dot com 2022-11-25 2:52 ` crazylht at gmail dot com 2022-11-25 5:16 ` crazylht at gmail dot com 2022-11-25 5:32 ` crazylht at gmail dot com 2022-11-25 6:06 ` crazylht at gmail dot com 2022-11-28 7:36 ` crazylht at gmail dot com 2022-11-29 6:17 ` crazylht at gmail dot com 2022-12-01 3:31 ` cvs-commit at gcc dot gnu.org 2022-12-01 3:33 ` cvs-commit at gcc dot gnu.org 2022-12-01 3:35 ` cvs-commit at gcc dot gnu.org 2022-12-01 3:37 ` cvs-commit at gcc dot gnu.org 2022-12-01 3:38 ` crazylht at gmail dot com 2022-12-01 15:45 ` 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-107863-4-6Fbi3iGb8X@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).