public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Jeff Law <jeffreyalaw@gmail.com>,
	Hans-Peter Nilsson <hp@axis.com>,
	Jeff Law <jlaw@ventanamicro.com>,
	 gcc-patches@gcc.gnu.org
Subject: Re: [committed] Enable LRA on several ports
Date: Mon, 22 May 2023 12:15:26 +0200	[thread overview]
Message-ID: <CAFiYyc0xsQ7cd9h2_rH6PpSsoK=GLieoXrXV4_5DfcbniAbQhw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2305190006350.50034@angie.orcam.me.uk>

On Fri, May 19, 2023 at 1:45 PM Maciej W. Rozycki <macro@orcam.me.uk> wrote:
>
> On Tue, 2 May 2023, Jeff Law via Gcc-patches wrote:
>
> > 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.
>
>  As I noted in the other thread it is highly unlikely I will make it with
> the VAX target in this release cycle, owing to the catastrophic breakage
> of the exception unwinder, recently discovered, which I consider higher
> priority as a show-stopper for important software such as current GDB.  I
> will appreciate your taking this into consideration.

You might end up with VAX working fine with reload for GCC 14 but
marked as deprecated.  You then have the full next cycle to GCC 15
to improve the code quality with LRA - note that reload is likely removed
early in the development cycle.

>  That written the VAX target does build its target libraries with `-mlra',
> but there are ICE regressions in the test suite and overall code produced
> is brown paperbag quality.  And removing `-mno-lra' before that has been
> sorted will make making LRA match old reload quality much tougher.

You can always compare to GCC 14 then or even work based off the
release branch.

Richard.

>   Maciej

  reply	other threads:[~2023-05-22 10:15 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
2023-05-19 11:44     ` Maciej W. Rozycki
2023-05-22 10:15       ` Richard Biener [this message]
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='CAFiYyc0xsQ7cd9h2_rH6PpSsoK=GLieoXrXV4_5DfcbniAbQhw@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hp@axis.com \
    --cc=jeffreyalaw@gmail.com \
    --cc=jlaw@ventanamicro.com \
    --cc=macro@orcam.me.uk \
    /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).