From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: 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: Fri, 19 May 2023 12:44:44 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2305190006350.50034@angie.orcam.me.uk> (raw)
In-Reply-To: <0bd369c5-cd8b-fa67-ef12-a3ee264f6a64@gmail.com>
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.
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.
Maciej
next prev parent reply other threads:[~2023-05-19 11:44 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 [this message]
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=alpine.DEB.2.21.2305190006350.50034@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@axis.com \
--cc=jeffreyalaw@gmail.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).