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/99321] [11 Regression] ICE: in extract_constrain_insn, at recog.c:2670: insn does not satisfy its constraints: {*uminv16qi3} since r11-7121-g37876976b0511ec9 Date: Mon, 01 Mar 2021 19:06:03 +0000 [thread overview] Message-ID: <bug-99321-4-TPC6zBj8Op@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99321-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99321 --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I'm afraid we have multiple problems with -mavx512vl -mno-avx512bw (are there any CPUs with that combination of ISA sets though?). In r7-618-g9bdf001b7a2232753e4a92582218bb4f24c8d809 I've fixed the 16-byte vp{min,max}ub to not allow v constraints when not AVX512BW. But clearly many other patterns need something like that and don't have that. E.g. vp{add,sub,{min,max},{u,s}}{b,w}, both 16-byte and 32-byte. The result of that aren't ICEs, but code silently using AVX512BW features when AVX512VL is enabled but AVX512BW is not. Similarly, vpmullq needs AVX512DQ. And, another thing is that the: (define_peephole2 [(set (match_operand 0 "sse_reg_operand") (match_operand 1 "sse_reg_operand")) (set (match_dup 0) (match_operator 3 "commutative_operator" [(match_dup 0) (match_operand 2 "memory_operand")]))] "REGNO (operands[0]) != REGNO (operands[1])" [(set (match_dup 0) (match_dup 2)) (set (match_dup 0) (match_op_dup 3 [(match_dup 0) (match_dup 1)]))]) peephole2 doesn't work and results in ICEs if the patterns are correct (as is the case of *uminv16qi3) if one is unlucky and operands[1] is [xy]mm16 or higher register and operands[0] is not.
next prev parent reply other threads:[~2021-03-01 19:06 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-01 15:53 [Bug target/99321] New: [11 Regression] ICE: in extract_constrain_insn, at recog.c:2670: insn does not satisfy its constraints: {*uminv16qi3} zsojka at seznam dot cz 2021-03-01 17:04 ` [Bug target/99321] [11 Regression] ICE: in extract_constrain_insn, at recog.c:2670: insn does not satisfy its constraints: {*uminv16qi3} since r11-7121-g37876976b0511ec9 marxin at gcc dot gnu.org 2021-03-01 17:05 ` jakub at gcc dot gnu.org 2021-03-01 19:06 ` jakub at gcc dot gnu.org [this message] 2021-03-02 17:18 ` jakub at gcc dot gnu.org 2021-03-03 9:07 ` cvs-commit at gcc dot gnu.org 2021-03-05 17:37 ` jakub at gcc dot gnu.org 2021-03-05 18:16 ` jakub at gcc dot gnu.org 2021-03-05 18:41 ` jakub at gcc dot gnu.org 2021-03-07 9:30 ` cvs-commit at gcc dot gnu.org 2021-03-12 13:36 ` cvs-commit at gcc dot gnu.org 2021-03-12 13:39 ` 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-99321-4-TPC6zBj8Op@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).