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 17:16:42 +0000 [thread overview]
Message-ID: <bug-97532-4-6hIl4uTYOE@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
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |liuhongt at gcc dot gnu.org,
| |vmakarov at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with r11-4203-g7026bb9504eb0f95e114f832cd6dd14302376861
We have:
(insn 87 4 5 2 (set (reg:DI 189)
(reg:DI 2 cx [ fact ])) "simd-2.f90":13:0 74 {*movdi_internal}
(expr_list:REG_DEAD (reg:DI 2 cx [ fact ])
(nil)))
...
(insn 76 75 81 2 (set (reg:V8DF 153 [ vect_c_20.334 ])
(plus:V8DF (vec_duplicate:V8DF (mem:DF (reg:DI 189) [6 *fact_18(D)+0 S8
A64]))
(reg:V8DF 184 [ vect__17.333 ]))) "simd-2.f90":18:0 1569
{*addv8df3}
(expr_list:REG_DEAD (reg:DI 189)
(expr_list:REG_DEAD (reg:V8DF 184 [ vect__17.333 ])
(nil))))
as the only insns that refer to pseudo 189, and for some reason IRA decides to
allocate that pseudo into xmm4 register which is not valid for memory
addresses.
So, something in the r11-4202 IRA changes doesn't work properly (and maybe
something in LRA too, because even if IRA decides to put it into such register,
which it e.g. could because 95% of uses would be in vector register contexts,
LRA should be able to fix it up, shouldn't it?
next prev parent reply other threads:[~2020-10-22 17:16 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 [this message]
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
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-6hIl4uTYOE@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).