From: Paul Koning <paulkoning@comcast.net>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Richard Biener <richard.guenther@gmail.com>,
Gerald Pfeifer <gerald@pfeifer.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] wwwdocs: Note that old reload is deprecated
Date: Wed, 11 Jan 2023 17:07:47 -0500 [thread overview]
Message-ID: <9D16702E-DC97-432C-A331-593FE242CE4C@comcast.net> (raw)
In-Reply-To: <20230111192850.GX25951@gate.crashing.org>
> On Jan 11, 2023, at 2:28 PM, Segher Boessenkool <segher@kernel.crashing.org> wrote:
>
> On Wed, Jan 11, 2023 at 01:42:22PM -0500, Paul Koning wrote:
>> Or, as in my case, because building with LRA as the default triggers an ICE that I don't understand. I posted a note to the GCC list about what I saw, but have received no reaction.
>
> <https://gcc.gnu.org/pipermail/gcc/2023-January/240497.html>?
I just saw that, thanks!
> I would say your predicates are way too lenient here (general_operand),
> but this needs more info. A testcase to reproduce the problem, to
> start with :-)
I'll try to trim it down.
What do you mean "too lenient"? The first input operand (which is supposed to be the same as the output since the instruction set is 2-address) is "general_operand". The destination is "nonimmediate_operand" which fits the constraints applied to it.
paul
next prev parent reply other threads:[~2023-01-11 22:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 19:27 Segher Boessenkool
2023-01-05 19:54 ` Paul Koning
2023-01-05 20:23 ` Segher Boessenkool
2023-01-11 14:21 ` Gerald Pfeifer
2023-01-11 14:34 ` Richard Biener
2023-01-11 15:15 ` Segher Boessenkool
2023-01-11 16:27 ` Richard Biener
2023-01-11 18:32 ` Segher Boessenkool
2023-01-11 18:39 ` Richard Biener
2023-01-11 19:07 ` Segher Boessenkool
2023-01-12 7:44 ` Richard Biener
2023-01-12 7:48 ` Richard Biener
2023-01-11 18:42 ` Paul Koning
2023-01-11 19:28 ` Segher Boessenkool
2023-01-11 22:07 ` Paul Koning [this message]
2023-01-12 9:50 ` Segher Boessenkool
2023-01-12 14:17 ` Paul Koning
2023-01-12 14:40 ` Segher Boessenkool
2023-01-12 15:07 ` Paul Koning
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=9D16702E-DC97-432C-A331-593FE242CE4C@comcast.net \
--to=paulkoning@comcast.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=richard.guenther@gmail.com \
--cc=segher@kernel.crashing.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).