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/97532] [11 Regression] Error: insn does not satisfy its constraints, internal compiler error: in extract_constrain_insn, at recog.c:2196
Date: Thu, 22 Oct 2020 19:03:30 +0000	[thread overview]
Message-ID: <bug-97532-4-iuDGzGv369@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97532-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The operand in this case is the whole
(vec_duplicate:V8DF (mem:DF (reg...) [6 *fact_18(D)+0 S8 A64]))
which matches the
(define_special_memory_constraint "Br"
  "@internal bcst memory operand."
  (match_operand 0 "bcst_mem_operand"))
constraint where bcst_mem_operand is:
(define_predicate "bcst_mem_operand"
  (and (match_code "vec_duplicate")
       (and (match_test "TARGET_AVX512F")
            (ior (match_test "TARGET_AVX512VL")
                 (match_test "GET_MODE_SIZE (GET_MODE (op)) == 64")))
       (match_test "VALID_BCST_MODE_P (GET_MODE_INNER (GET_MODE (op)))")
       (match_test "memory_operand (XEXP (op, 0), GET_MODE (XEXP (op, 0)))")))
I think the extract_mem_from_operand function has been introduced for this in
LRA, but perhaps it is not used in all the places where it is needed.

  parent reply	other threads:[~2020-10-22 19:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-22 16:12 [Bug libgomp/97532] New: " vries at gcc dot gnu.org
2020-10-22 16:32 ` [Bug target/97532] [11 Regression] " rguenth at gcc dot gnu.org
2020-10-22 17:16 ` jakub at gcc dot gnu.org
2020-10-22 18:19 ` jakub at gcc dot gnu.org
2020-10-22 18:48 ` vmakarov at gcc dot gnu.org
2020-10-22 19:03 ` jakub at gcc dot gnu.org [this message]
2020-10-23  5:49 ` crazylht at gmail dot com
2020-10-23  7:42 ` jakub at gcc dot gnu.org
2020-10-23  8:11 ` crazylht at gmail dot com
2020-10-23 15:21 ` vmakarov at gcc dot gnu.org
2020-10-27  6:05 ` crazylht at gmail dot com
2020-10-28  9:40 ` rguenth at gcc dot gnu.org
2020-10-29 12:36 ` vries at gcc dot gnu.org
2020-10-30  0:54 ` crazylht at gmail dot com
2020-11-04  5:07 ` cvs-commit at gcc dot gnu.org
2020-11-04  5:13 ` crazylht at gmail dot com
2020-11-18 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-97532-4-iuDGzGv369@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).