From: Richard Biener <richard.guenther@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Gerald Pfeifer <gerald@pfeifer.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] wwwdocs: Note that old reload is deprecated
Date: Thu, 12 Jan 2023 08:48:32 +0100 [thread overview]
Message-ID: <CAFiYyc1WYTXajzAe6jeZJYQ9RLCHFD4J03Tpi2qSGCBON5XRKA@mail.gmail.com> (raw)
In-Reply-To: <CAFiYyc0F7JK_fN-t+2xKvR66zs+U_YjOorqz4J-dshgt9ceqAw@mail.gmail.com>
On Thu, Jan 12, 2023 at 8:44 AM Richard Biener
<richard.guenther@gmail.com> wrote:
>
> On Wed, Jan 11, 2023 at 8:09 PM Segher Boessenkool
> <segher@kernel.crashing.org> wrote:
> >
> > On Wed, Jan 11, 2023 at 07:39:29PM +0100, Richard Biener wrote:
> > > Like if they cannot even build their target libraries aka their build will fail. It would be nice to identify those and, say, make at least -mlra available to all ports that currently do not have a way to enable LRA?
> >
> > It is up to the target maintainers to make such support, it is a machine
> > flag after all (-m are machine flags, -f are more general flags).
> >
> > There has been ample warning, see <https://gcc.gnu.org/wiki/LRAIsDefault>
> > for example. GCC 13 release will be six years after that, I'd hope that
> > that is enough.
> >
> > Just using
> > targetm.lra_p = default_lra_p;
> > is enough to test. I don't have a setup to build all targets (that
> > requires target headers, to begin with), and it is up to the target
> > maintainers to decide how they want things fixed anyway.
> >
> > I'll put up a preliminary branch for the generic patches, but let me
> > update it to trunk first :-)
>
> Just saying that the changes.html note has not much information but instead will
> spread FUD without indicating which ports would be dysfunctional after removing
> reload support (aka will even no longer build). So I'd say we don't want this
> note in changes.html in the proposed form.
Btw, the following is the ports that default to reload and have no command line
option to switch to LRA.
config/alpha/alpha.cc:#define TARGET_LRA_P hook_bool_void_false
config/avr/avr.cc:#define TARGET_LRA_P hook_bool_void_false
config/bfin/bfin.cc:#define TARGET_LRA_P hook_bool_void_false
config/c6x/c6x.cc:#define TARGET_LRA_P hook_bool_void_false
config/cris/cris.cc:#define TARGET_LRA_P hook_bool_void_false
config/epiphany/epiphany.cc:#define TARGET_LRA_P hook_bool_void_false
config/fr30/fr30.cc:#define TARGET_LRA_P hook_bool_void_false
config/frv/frv.cc:#define TARGET_LRA_P hook_bool_void_false
config/h8300/h8300.cc:#define TARGET_LRA_P hook_bool_void_false
config/ia64/ia64.cc:#define TARGET_LRA_P hook_bool_void_false
config/iq2000/iq2000.cc:#define TARGET_LRA_P hook_bool_void_false
config/lm32/lm32.cc:#define TARGET_LRA_P hook_bool_void_false
config/m32c/m32c.cc:#define TARGET_LRA_P hook_bool_void_false
config/m32r/m32r.cc:#define TARGET_LRA_P hook_bool_void_false
config/m68k/m68k.cc:#define TARGET_LRA_P hook_bool_void_false
config/mcore/mcore.cc:#define TARGET_LRA_P hook_bool_void_false
config/microblaze/microblaze.cc:#define TARGET_LRA_P hook_bool_void_false
config/mmix/mmix.cc:#define TARGET_LRA_P hook_bool_void_false
config/mn10300/mn10300.cc:#define TARGET_LRA_P hook_bool_void_false
config/moxie/moxie.cc:#define TARGET_LRA_P hook_bool_void_false
config/msp430/msp430.cc:#define TARGET_LRA_P hook_bool_void_false
config/nvptx/nvptx.cc:#define TARGET_LRA_P hook_bool_void_false
config/pa/pa.cc:#define TARGET_LRA_P hook_bool_void_false
config/rl78/rl78.cc:#define TARGET_LRA_P hook_bool_void_false
config/stormy16/stormy16.cc:#define TARGET_LRA_P hook_bool_void_false
config/visium/visium.cc:#define TARGET_LRA_P hook_bool_void_false
next prev parent reply other threads:[~2023-01-12 7:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 19:27 Segher Boessenkool
2023-01-05 19:54 ` Paul Koning
2023-01-05 20:23 ` Segher Boessenkool
2023-01-11 14:21 ` Gerald Pfeifer
2023-01-11 14:34 ` Richard Biener
2023-01-11 15:15 ` Segher Boessenkool
2023-01-11 16:27 ` Richard Biener
2023-01-11 18:32 ` Segher Boessenkool
2023-01-11 18:39 ` Richard Biener
2023-01-11 19:07 ` Segher Boessenkool
2023-01-12 7:44 ` Richard Biener
2023-01-12 7:48 ` Richard Biener [this message]
2023-01-11 18:42 ` Paul Koning
2023-01-11 19:28 ` Segher Boessenkool
2023-01-11 22:07 ` Paul Koning
2023-01-12 9:50 ` Segher Boessenkool
2023-01-12 14:17 ` Paul Koning
2023-01-12 14:40 ` Segher Boessenkool
2023-01-12 15:07 ` Paul Koning
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=CAFiYyc1WYTXajzAe6jeZJYQ9RLCHFD4J03Tpi2qSGCBON5XRKA@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--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).