From: Vladimir Makarov <vmakarov@redhat.com>
To: gcc@gcc.gnu.org
Subject: Re: Special Memory Constraint [was Re: Indirect memory addresses vs. lra]
Date: Mon, 19 Aug 2019 13:14:00 -0000 [thread overview]
Message-ID: <16f173b7-d835-48f9-aaed-d5d38d4748ca@redhat.com> (raw)
In-Reply-To: <20190819073553.pi644qzyokxmynr2@jocasta.intra>
On 2019-08-19 3:35 a.m., John Darrington wrote:
> On Fri, Aug 16, 2019 at 10:50:13AM -0400, Vladimir Makarov wrote:
>
>
> No I meant something like that
>
> (define_special_memory_constraint "a" ...)
> (define_predicate "my_special_predicate" ...
>
> {
> if (lra_in_progress_p)
> return REG_P (op) && REGNO (op) >= FIRST_PSEUDO_REGISTER && reg_renumber[REGNO(op)] < 0;
> return true if memory with sp addressing;
> })
>
> I think LRA spills pseudo-register and it will be memory addressed by sp
> at the end of LRA.
>
> What I've done is this:
>
> (define_predicate "my_special_predicate"
> (match_operand 0 "memory_operand")
> {
> debug_rtx (op);
> gcc_assert (MEM_P (op));
> op = XEXP (op, 0);
> if (GET_CODE (op) == PLUS)
> op = XEXP (op, 0);
>
> if (lra_in_progress)
> {
> fprintf (stderr, "%s:%d\n", __FILE__, __LINE__);
> return REG_P (op) && REGNO (op) >= FIRST_PSEUDO_REGISTER && reg_renumber[REGNO(op)] < 0;
> }
>
>
> if (REG_P (op))
> {
> int regno = REGNO (op);
> return (regno == 10); // register is the stack pointer
> }
>
> return true;
> })
>
> (and many variations) Unfortunately, any moderately complicated input
> still results in a (mem (reg) ) insn repeatedly entering the
> lra_in_progress case and returning false, and eventually terminating with
>
> "internal compiler error: maximum number of generated reload insns per insn achieved (90)"
>
>
> Any other ideas?
 As I remember there were a few other ideas from Richard Biener and
Segher Boessenkool. I also proposed to add a new address register which
will be always a fixed stack memory slot at the end. Unfortunately I am
not familiar with the target and the port to say in details how to do
it. But I think it is worth to try.
next prev parent reply other threads:[~2019-08-19 13:14 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-04 19:18 Indirect memory addresses vs. lra John Darrington
2019-08-08 16:25 ` Vladimir Makarov
2019-08-08 16:44 ` Paul Koning
2019-08-08 17:21 ` Segher Boessenkool
2019-08-08 17:25 ` Paul Koning
2019-08-08 19:09 ` Segher Boessenkool
2019-08-08 17:30 ` Paul Koning
2019-08-08 19:19 ` Segher Boessenkool
2019-08-08 19:57 ` Jeff Law
2019-08-09 8:14 ` John Darrington
2019-08-09 14:17 ` Segher Boessenkool
2019-08-09 14:23 ` Paul Koning
2019-08-10 6:10 ` John Darrington
2019-08-10 16:15 ` Segher Boessenkool
2019-08-09 16:07 ` Jeff Law
2019-08-09 17:34 ` Vladimir Makarov
2019-08-10 6:06 ` John Darrington
2019-08-10 16:12 ` Segher Boessenkool
2019-08-12 6:47 ` John Darrington
2019-08-12 8:40 ` Segher Boessenkool
2019-08-12 13:35 ` Vladimir Makarov
2019-08-15 16:29 ` Vladimir Makarov
2019-08-15 16:38 ` Richard Biener
2019-08-15 17:41 ` John Darrington
2019-08-15 18:30 ` Vladimir Makarov
2019-08-15 21:22 ` Segher Boessenkool
2019-08-15 17:36 ` John Darrington
2019-08-15 18:23 ` Vladimir Makarov
2019-08-16 11:24 ` Special Memory Constraint [was Re: Indirect memory addresses vs. lra] John Darrington
2019-08-16 14:50 ` Vladimir Makarov
2019-08-19 7:36 ` John Darrington
2019-08-19 13:14 ` Vladimir Makarov [this message]
2019-08-19 15:07 ` Segher Boessenkool
2019-08-19 18:06 ` John Darrington
2019-08-20 6:56 ` Richard Biener
2019-08-20 7:07 ` John Darrington
2019-08-20 7:30 ` Richard Biener
2019-08-08 18:46 ` Indirect memory addresses vs. lra 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=16f173b7-d835-48f9-aaed-d5d38d4748ca@redhat.com \
--to=vmakarov@redhat.com \
--cc=gcc@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).