From: "Roger Sayle" <roger@nextmovesoftware.com>
To: "'Paul Koning'" <paulkoning@comcast.net>
Cc: "'Jeff Law'" <jeffreyalaw@gmail.com>,
"'GCC Patches'" <gcc-patches@gcc.gnu.org>,
"'Segher Boessenkool'" <segher@kernel.crashing.org>
Subject: RE: [committed] Convert xstormy16 to LRA
Date: Tue, 2 May 2023 14:18:43 +0100 [thread overview]
Message-ID: <021801d97cf8$9fc91770$df5b4650$@nextmovesoftware.com> (raw)
In-Reply-To: <0FD01909-1F42-4E50-8D0D-2EDB80C34C0A@comcast.net>
On 02 May 2023 13:40, Paul Koning wrote:
> > On May 1, 2023, at 7:37 PM, Roger Sayle <roger@nextmovesoftware.com>
> wrote:
> >
> > ...
> > The shiftsi.cc regression on xstormy16 is fixed by adding
> > -fno-split-wide-types.
> > In fact, if all the regression tests pass, I'd suggest that
> > flag_split_wide-types = false should be the default on xstormy16 now
> > that we've moved to LRA. And if this works for xstormy16, it might be
> > useful to other targets for the LRA transition; it's a difference in
> > behaviour between reload and LRA that could potentially affect
> > multiple targets.
>
> Is there documentation for that flag?
Yes, see the section -fsplit-wide-types in
https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html
Interestingly, there's a recent-ish blog describing how
-fno-split-wide-types
reduces executable size on AVR:
https://ufj.ddns.net/blog/marlin/2019/01/07/reducing-marlin-binary-size.html
and its interaction with (AVR) register allocation is seen in PR
middle-end/35860.
Cheers,
Roger
--
next prev parent reply other threads:[~2023-05-02 13:18 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 [this message]
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
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='021801d97cf8$9fc91770$df5b4650$@nextmovesoftware.com' \
--to=roger@nextmovesoftware.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=paulkoning@comcast.net \
--cc=segher@kernel.crashing.org \
/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).