From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Koning, Paul" <Paul.Koning@dell.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Always enable LRA
Date: Fri, 14 Oct 2022 11:18:35 -0500 [thread overview]
Message-ID: <20221014161835.GC25951@gate.crashing.org> (raw)
In-Reply-To: <32000BFD-260F-4364-8F8F-6167BD3DE510@dell.com>
On Fri, Oct 14, 2022 at 12:36:47AM +0000, Koning, Paul wrote:
> I guess I'll have to look harder to see if it's possible to make LRA handle CISC addressing modes like memory indirect, autoincrement, autodecrement, and others that the old reload handles at least somewhat. Ideally LRA should do a better job; right now I believe it doesn't really do these things at all. Targets like pdp11 and vax would like these.
So what does it do now? Break every more complex addressing mode apart
again? Or ICE? Or something in between?
Segher
next prev parent reply other threads:[~2022-10-14 16:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 23:56 Segher Boessenkool
2022-10-14 0:36 ` Koning, Paul
2022-10-14 16:18 ` Segher Boessenkool [this message]
2022-10-14 16:48 ` Koning, Paul
2022-10-14 1:07 ` Jeff Law
2022-10-14 12:37 ` Koning, Paul
2022-10-14 14:38 ` Jeff Law
2022-10-14 16:37 ` Koning, Paul
2022-10-14 17:10 ` Jeff Law
2022-10-14 17:36 ` Koning, Paul
2022-10-14 21:15 ` Jeff Law
2022-10-14 21:21 ` Koning, Paul
2022-10-14 21:30 ` Jeff Law
2022-10-15 0:19 ` Jeff Law
2022-10-14 16:39 ` Richard Biener
2022-10-14 17:11 ` Jeff Law
2022-10-14 4:47 ` Jeff Law
2022-10-14 16:37 ` Segher Boessenkool
2022-10-14 17:07 ` Jeff Law
2022-10-14 17:35 ` Segher Boessenkool
2022-10-14 18:03 ` Jeff Law
2022-10-14 19:58 ` Koning, Paul
2022-10-14 20:12 ` Segher Boessenkool
2022-10-14 20:40 ` Koning, Paul
2022-10-14 6:20 ` Takayuki 'January June' Suwa
2022-10-14 16:25 ` Segher Boessenkool
2022-10-15 3:18 ` Takayuki 'January June' Suwa
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=20221014161835.GC25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=Paul.Koning@dell.com \
--cc=gcc-patches@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).