From: Segher Boessenkool <segher@kernel.crashing.org>
To: Peter Bergner <bergner@linux.ibm.com>
Cc: Jeff Law <law@redhat.com>,
Vladimir N Makarov <vmakarov@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [RFC][PATCH LRA] WIP patch to fix one part of PR87507
Date: Tue, 23 Oct 2018 04:54:00 -0000 [thread overview]
Message-ID: <20181023002007.GF5205@gate.crashing.org> (raw)
In-Reply-To: <d944b375-bae4-819f-5043-54ad085bebb0@linux.ibm.com>
Hi peter,
On Mon, Oct 22, 2018 at 06:40:58PM -0500, Peter Bergner wrote:
> --- gcc/function.c (revision 265399)
> +++ gcc/function.c (working copy)
> @@ -6453,6 +6453,13 @@ match_asm_constraints_1 (rtx_insn *insn,
> || !general_operand (input, GET_MODE (output)))
> continue;
>
> + /* If we have a matching constraint and both operands are hard registers,
> + then they must be the same hard register. */
> + if (HARD_REGISTER_P (output)
> + && HARD_REGISTER_P (input)
> + && REGNO (output) != REGNO (input))
You need to test for REG_P (input) before you can HARD_REGISTER_P (input)
or REGNO (input).
> + fatal_insn ("unable to fixup asm constraints for:", insn);
"impossible constraints"? There are some more of those already. Or you
could describe the actual problem even?
> + /* Operands don't match. Make sure the two operands
> + are not two different explicit hard registers. */
> + if (HARD_REGISTER_P (*curr_id->operand_loc[nop])
> + && HARD_REGISTER_P (*curr_id->operand_loc[m]))
> + fatal_insn ("unable to generate reloads for:",
> + curr_insn);
Same here (and below) :-)
Segher
next prev parent reply other threads:[~2018-10-23 0:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 21:51 Peter Bergner
2018-10-20 6:47 ` Peter Bergner
2018-10-20 21:05 ` Segher Boessenkool
2018-10-22 22:08 ` Jeff Law
2018-10-23 0:25 ` Peter Bergner
2018-10-23 1:16 ` Peter Bergner
2018-10-27 23:25 ` Peter Bergner
2018-11-06 20:28 ` Jeff Law
2018-11-07 0:14 ` Segher Boessenkool
2018-11-07 16:29 ` Peter Bergner
2018-11-07 17:36 ` Jeff Law
2018-11-07 17:45 ` Peter Bergner
2018-11-08 2:17 ` Peter Bergner
2018-11-08 22:07 ` Jeff Law
2018-11-08 22:42 ` Peter Bergner
2018-10-23 4:54 ` Segher Boessenkool [this message]
2018-10-23 6:47 ` Peter Bergner
2018-10-25 0:55 ` Jeff Law
2018-10-20 17:23 ` Segher Boessenkool
2018-10-22 23:23 ` Vladimir Makarov
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=20181023002007.GF5205@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=bergner@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=vmakarov@redhat.com \
/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).