public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Hans-Peter Nilsson <hp@axis.com>, Jeff Law <jlaw@ventanamicro.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [committed] Enable LRA on several ports
Date: Tue, 2 May 2023 10:41:15 -0600	[thread overview]
Message-ID: <0bd369c5-cd8b-fa67-ef12-a3ee264f6a64@gmail.com> (raw)
In-Reply-To: <20230502032401.A270320418@pchp3.se.axis.com>



On 5/1/23 21:24, Hans-Peter Nilsson via Gcc-patches wrote:

> 
>>     There may be
>> minor code quality regressions or there may be minor code quality
>> improvements -- I'm leaving that for the port maintainers to own going
>> forward.
> 
> Right; I noticed performance regressions, and didn't want to
> commit anything that knowingly degraded performance.  I did
> follow the traces but fell into the rabbit-hole of
> rtx_costs.  That's the main reason I didn't push a "-mlra"
> option or remove the TARGET_LRA_P for CRIS.  (My story and I
> stick to it.)
> 
> But thanks I guess, it saves me a commit, but (to all!)
> please sync check_effective_target_lra for targets you
> "convert".  ...oops, it's just CRIS and hppa there (wot, not
> converted?)
Well, I'd say that my plan would be to deprecate any target that is not 
converted by the end of this development cycle.  So the change keeps 
cris from falling into that bucket.

I wasn't aware of check_effective_target_lra.  Thanks.  I'll make sure 
to get that updated as we go forward.

jeff

  reply	other threads:[~2023-05-02 16:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-01 13:21 Jeff Law
2023-05-02  3:24 ` Hans-Peter Nilsson
2023-05-02 16:41   ` Jeff Law [this message]
2023-05-19 11:44     ` Maciej W. Rozycki
2023-05-22 10:15       ` Richard Biener
2023-08-14  2:11 ` Hans-Peter Nilsson
2023-11-10 23:52   ` Jeff Law

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=0bd369c5-cd8b-fa67-ef12-a3ee264f6a64@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hp@axis.com \
    --cc=jlaw@ventanamicro.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).