From: Hans-Peter Nilsson <hp@axis.com>
To: Roger Sayle <roger@nextmovesoftware.com>
Cc: <jeffreyalaw@gmail.com>, <gcc-patches@gcc.gnu.org>,
<segher@kernel.crashing.org>, <vmakarov@redhat.com>
Subject: Re: [committed] Convert xstormy16 to LRA
Date: Sat, 13 May 2023 02:56:39 +0200 [thread overview]
Message-ID: <20230513005639.2E4FC203FA@pchp3.se.axis.com> (raw)
In-Reply-To: <009601d984da$9d4322e0$d7c968a0$@nextmovesoftware.com> (roger@nextmovesoftware.com)
> From: "Roger Sayle" <roger@nextmovesoftware.com>
> Date: Fri, 12 May 2023 15:04:03 +0100
> Hi H-P,
> This patch should now already be on trunk:
> https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=d8a6945c6ea22efa4d5e42fe1922d2
> b27953c8cd
> Many thanks to Jeff for the review/approval.
> There have been no reported adverse effects so far.
> Please let me/us know if this has helped CRIS.
TL;DR:
It sure helped for the big offender; arith-rand-ll with LRA
is now 1.3% faster! Not everything is rosy though.
It's not a complete win for CRIS with LRA, as other of my
mini-regression tests (like, a trivial loop with 0<=i<=10
fprintf (f, "%s: %d\n", "Hello, world", i); with newlib),
where it got 0.04% larger. On average though, 0.5% smaller.
Actually, it's more accurate to state it in terms of the
code that changed: newlib's _vfprintf_r improved slightly
performance-wise on some paths (1 cycle per call), but
regressed on others (7 cycles per call). It got 0.2%
bigger. Libgcc's __moddi3 regressed slightly (1 cycle per
11 calls) but stayed the same size. The main function in
arith-rand-ll (where I guess all small functions got
inlined) improved 3% by size, performance as above.
Those clobbers must have helped reload, because with reload
there was a 0.15% performance regression for arith-rand-ll
(and 0.2% by size because main got 1.6% larger) with this
patch. But size was smaller or equal for all other tests
using reload with this patch, if only by 0.04% on average.
Or in other numbers: _vfprintf_r got 4 cycles faster per
call on some paths and 2 on others. It got 0.05% bigger. A
similar function, __vfiprintf_r, shrank by 0.5%. Go figure.
For all but arith-rand-ll, this patch was a wash for reload.
(Yes: the case with reload is now artificial; for that, I
was using master before Jeff's commit and added my own
commits since then, to keep track of my fight against LRA
regressions; the current score is that code is still 0.34%
slower and 0.17% larger with this applied just for LRA.)
Can we ask Vladimir for a statement; perhaps LRA could just
have handled those clobbers better (referring to the commit)?
brgds, H-P
next prev parent reply other threads:[~2023-05-13 0:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 23:37 Roger Sayle
2023-05-02 12:40 ` Paul Koning
2023-05-02 13:18 ` Roger Sayle
2023-05-02 13:49 ` Segher Boessenkool
2023-05-02 16:20 ` Roger Sayle
2023-05-02 21:55 ` Segher Boessenkool
2023-05-02 14:11 ` Paul Koning
2023-05-02 15:47 ` Segher Boessenkool
2023-05-02 15:57 ` Jeff Law
2023-05-11 15:05 ` Hans-Peter Nilsson
2023-05-11 16:55 ` Paul Koning
2023-05-11 18:15 ` Jeff Law
2023-05-11 18:32 ` Hans-Peter Nilsson
2023-05-12 13:53 ` Hans-Peter Nilsson
2023-05-12 14:01 ` Hans-Peter Nilsson
2023-05-12 14:04 ` Roger Sayle
2023-05-13 0:56 ` Hans-Peter Nilsson [this message]
2023-05-13 1:11 ` Hans-Peter Nilsson
-- strict thread matches above, loose matches on Subject: below --
2023-05-01 13:42 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=20230513005639.2E4FC203FA@pchp3.se.axis.com \
--to=hp@axis.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=roger@nextmovesoftware.com \
--cc=segher@kernel.crashing.org \
--cc=vmakarov@redhat.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).