public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/103623] [12 Regression] error: unable to generate reloads (ICE in curr_insn_transform, at lra-constraints.c:4132), or error: insn does not satisfy its constraints (ICE in extract_constrain_insn_cached, at recog.c:2682)
Date: Mon, 11 Apr 2022 21:02:49 +0000 [thread overview]
Message-ID: <bug-103623-4-akGAokjcmV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103623-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103623
--- Comment #32 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Segher Boessenkool <segher@gcc.gnu.org>:
https://gcc.gnu.org/g:0508f0b810985f4a8543ce44701ec7330ef29796
commit r12-8091-g0508f0b810985f4a8543ce44701ec7330ef29796
Author: Segher Boessenkool <segher@kernel.crashing.org>
Date: Mon Apr 11 15:43:38 2022 +0000
rs6000: Fix unpack for no-direct-move (PR103623)
The _dm alternative works fine for soft-float, but the _nodm variant
pattern is missing that alternative. So, let's add that.
There probably should be an r,r,i alternative as well (or we can make it
rm,r,i), but that is for later.
2022-04-11 Segher Boessenkool <segher@kernel.crashing.org>
PR target/105213
PR target/103623
* config/rs6000/rs6000.md (unpack<mode>_nodm): Add m,r,i
alternative.
next prev parent reply other threads:[~2022-04-11 21:02 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 10:42 [Bug target/103623] New: " asolokha at gmx dot com
2021-12-10 1:49 ` [Bug target/103623] " linkw at gcc dot gnu.org
2021-12-10 2:32 ` [Bug target/103623] [12 Regression] " pinskia at gcc dot gnu.org
2021-12-10 9:11 ` linkw at gcc dot gnu.org
2021-12-10 13:27 ` wschmidt at gcc dot gnu.org
2021-12-10 20:56 ` bergner at gcc dot gnu.org
2021-12-12 17:29 ` wschmidt at gcc dot gnu.org
2021-12-12 17:44 ` wschmidt at gcc dot gnu.org
2021-12-13 2:45 ` asolokha at gmx dot com
2021-12-13 16:17 ` wschmidt at gcc dot gnu.org
2021-12-14 17:20 ` cvs-commit at gcc dot gnu.org
2021-12-14 17:26 ` wschmidt at gcc dot gnu.org
2021-12-22 10:48 ` asolokha at gmx dot com
2021-12-23 3:35 ` linkw at gcc dot gnu.org
2021-12-23 5:05 ` asolokha at gmx dot com
2021-12-27 2:26 ` linkw at gcc dot gnu.org
2021-12-27 2:27 ` linkw at gcc dot gnu.org
2021-12-27 3:28 ` asolokha at gmx dot com
2021-12-27 5:13 ` linkw at gcc dot gnu.org
2021-12-27 5:25 ` asolokha at gmx dot com
2021-12-27 5:45 ` asolokha at gmx dot com
2021-12-27 6:25 ` linkw at gcc dot gnu.org
2021-12-27 6:36 ` linkw at gcc dot gnu.org
2021-12-27 6:42 ` asolokha at gmx dot com
2021-12-27 6:51 ` asolokha at gmx dot com
2022-01-18 14:11 ` rguenth at gcc dot gnu.org
2022-02-17 2:07 ` linkw at gcc dot gnu.org
2022-02-18 8:38 ` linkw at gcc dot gnu.org
2022-02-18 8:44 ` linkw at gcc dot gnu.org
2022-02-18 17:22 ` segher at gcc dot gnu.org
2022-02-18 19:58 ` bergner at gcc dot gnu.org
2022-02-18 21:57 ` segher at gcc dot gnu.org
2022-02-18 22:00 ` segher at gcc dot gnu.org
2022-02-21 3:03 ` linkw at gcc dot gnu.org
2022-04-11 21:02 ` cvs-commit at gcc dot gnu.org [this message]
2022-04-12 1:40 ` linkw at gcc dot gnu.org
2022-04-21 18:02 ` segher 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-103623-4-akGAokjcmV@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).