Richard Biener <rguent...@suse.de> writes: > The following amends gcc-15/changes.html with a note that reload > is going to be removed for GCC 16. > > OK for www? > > * htdocs/gcc-15/changes.html: Mark GCC 15 as last release > supporting reload.
My reading of the threads was that no-one is objecting to this timeline, just giving status updates about how it will affect the ports that they care about. And in any case, the transition period has already been quite a bit longer than originally planned. On that basis: LGTM, thanks. Richard > --- > htdocs/gcc-15/changes.html | 7 +++++++ > 1 file changed, 7 insertions(+) > > 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 > + 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> > <li><code>{0}</code> initializer in C or C++ for unions no longer > guarantees clearing of the whole union (except for static storage > duration initialization), it just initializes the first
