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: Wed, 11 Jan 2023 19:39:29 +0100 [thread overview]
Message-ID: <D3366CD2-751D-49BD-8C7C-60DAA64A82BA@gmail.com> (raw)
In-Reply-To: <20230111183251.GV25951@gate.crashing.org>
> Am 11.01.2023 um 19:34 schrieb Segher Boessenkool <segher@kernel.crashing.org>:
>
> On Wed, Jan 11, 2023 at 05:27:36PM +0100, Richard Biener wrote:
>>>> Am 11.01.2023 um 16:17 schrieb Segher Boessenkool <segher@kernel.crashing.org>:
>>>>> Note this is more info for port maintainers not for users and
>>>>> changes.html is for users.
>>>
>>> And users will notice some ports will have to be removed, because those
>>> ports are not maintained / not maintained enough. Some ports will not
>>> work with LRA, most will be easy to fix, but someone will have to do
>>> that. If no one does so the port works sufficiently well it will have
>>> to be removed before release.
>>>
>>>> "In a future release" is also quite vague.
>>>
>>> It's what we usually say in changes.html . "In GCC 14" if you want?
>>>
>>> I can add some stuff on how this will benefit users?
>>
>> I guess listing the ports without LRA support might be a first step for clarification?
>
> Every port has LRA support.
>
> Some ports will not build later when we delete old reload, because they
> use some functions and/or data structures unique to that.
>
> But all that is easily fixed (for the port maintainers at least,
> assuming they understand what their code does ;-) ). The bigger problem
> is that if the port has never been tested with LRA the chances of it
> working in all cases are not great (say 50%), so likely some attention
> will be needed to get the compiler back to release quality. And some
> ports will even not work for the simplest pieces of source code. Those
> are the problematic cases.
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?
Richard
> Usually not hard to fix -- all the more complicated targets already run
> LRA always, the hard work is done already -- but it still requires a
> target maintainer (with a suitable testing environment, hopefully even
> hardware) to do the work. This is what I want to alert people to, and
> get agreement that this will happen next major release.
>
>
> Segher
next prev parent reply other threads:[~2023-01-11 18:39 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 [this message]
2023-01-11 19:07 ` Segher Boessenkool
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=D3366CD2-751D-49BD-8C7C-60DAA64A82BA@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).