From: Hans-Peter Nilsson <hp@bitrange.com>
To: Jeff Law <jlaw@ventanamicro.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [committed] Enable LRA on several ports
Date: Sun, 13 Aug 2023 22:11:21 -0400 (EDT) [thread overview]
Message-ID: <alpine.BSF.2.20.16.2308121635380.21217@arjuna.pair.com> (raw)
In-Reply-To: <91be1ec3-de85-04cc-0d9f-d3aa69f075dc@ventanamicro.com>
On Mon, 1 May 2023, Jeff Law wrote:
>
> Spurred by Segher's RFC, I went ahead and tested several ports with LRA
> enabled. Not surprisingly, many failed, but a few built their full set of
> libraries successful and of those a few even ran their testsuites with no
> regressions. In fact, enabling LRA fixes a small number of failures on the
> iq2000 port.
>
> This patch converts the ports which built their libraries and have test
> results that are as good as or better than without LRA. 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.
How do you configure your builds? Perhaps your cross-builds
exclude C++? I found that this (r14-383) broke MMIX building
libstdc++-v3 from that commit up to and including r14-3180.
See commit r14-3187.
Thankfully there was just one single gotcha. I temporarily
reverted the LRA change for MMIX so that I can get honest
repeatable baseline results. There seems to have been one
test-case regressing from the LRA switch (PR53948), thus I
re-enabled LRA for MMIX again. Sorry for the late reaction.
brgds, H-P
next prev parent reply other threads:[~2023-08-14 2:11 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
2023-08-14 2:11 ` Hans-Peter Nilsson [this message]
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.BSF.2.20.16.2308121635380.21217@arjuna.pair.com \
--to=hp@bitrange.com \
--cc=gcc-patches@gcc.gnu.org \
--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).