On Fri, May 02, 2025 at 12:26:12PM +0200, Richard Biener wrote:
> The following amends gcc-15/changes.html with a note that reload
> is going to be removed for GCC 16.

Thank you!  The patches are taking a little time, I gave up on rebasing
what I had, redoing it is less work.  Oh well.

> OK for www?
> 
>       * htdocs/gcc-15/changes.html: Mark GCC 15 as last release
>       supporting reload.

It looks fine to me, but I'm of course not an HTML expert (not since 30
or so years anymore :-) )

> diff --git a/htdocs/gcc-15/changes.html b/htdocs/gcc-15/changes.html
> index d851a744..4b1fd284 100644
> --- a/htdocs/gcc-15/changes.html
> +++ b/htdocs/gcc-15/changes.html
> @@ -31,6 +31,13 @@ You may also want to check out our
>    <li>In the AArch64 port, support for ILP32 (<code>-mabi=ilp32</code>) has
>      been deprecated and will be removed in a future release.
>    </li>
> +  <li>This is the last release supporting the old <code>reload</code> local
> +    register allocation code.  It will be removed for GCC 16, causing

Interesting that you call old reload "local register allocation", hehe.

> +    targets that do not support the new <code>LRA</code> local register
> +    allocation code to be removed.  See the list of supported
> +    <a href="https://gcc.gnu.org/backends.html";>targets</a> for which
> +    ports are going to be affected (look for missing <code>a</code>, the
> +    ports that do not use LRA by default).</li>

(That reminds me I need to add a patch to remove that "a" code!  Well,
"add", it is in a different repo, but heh.)

Everything *will* use LRA, after the upcoming changes.  Some ports will
not build, and some will build but not work at all, and those indeed
should be removed (or get some last-minute updates -- I'm the eternal
optimist).  This is not a new or separate policy, they will simply be
broken ports then.

Many ports that newly use LRA will hit some problems for unusual things.
most of those will be trivial to fix, but some might require changes to
generic parts of the compiler, like to LRA itself.  It would have been
really good if ports that have such difficulties had tried to use LRA
before!  But here we are.


Segher

Reply via email to