From: Segher Boessenkool <segher@kernel.crashing.org>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Gerald Pfeifer <gerald@pfeifer.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] wwwdocs: Note that old reload is deprecated
Date: Wed, 11 Jan 2023 13:07:19 -0600 [thread overview]
Message-ID: <20230111190719.GW25951@gate.crashing.org> (raw)
In-Reply-To: <D3366CD2-751D-49BD-8C7C-60DAA64A82BA@gmail.com>
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 :-)
Segher
next prev parent reply other threads:[~2023-01-11 19:08 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 [this message]
2023-01-12 7:44 ` Richard Biener
2023-01-12 7:48 ` Richard Biener
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=20230111190719.GW25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=richard.guenther@gmail.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).