diff mbox series

[htdocs] bugs: Link to all 'Porting to' docs in 'Common problems when upgrading ...'

Message ID 862c5bb071859ae156b994c86954d66ab1f14888.1739353540.git.sam@gentoo.org
State New
Headers
Series [htdocs] bugs: Link to all 'Porting to' docs in 'Common problems when upgrading ...' |

Checks

Context Check Description
linaro-tcwg-bot/tcwg_gcc_build--master-aarch64 fail Patch failed to apply
linaro-tcwg-bot/tcwg_simplebootstrap_build--master-aarch64-bootstrap fail Patch failed to apply
linaro-tcwg-bot/tcwg_simplebootstrap_build--master-arm-bootstrap fail Patch failed to apply
linaro-tcwg-bot/tcwg_gcc_build--master-arm fail Patch failed to apply

Commit Message

Sam James Feb. 12, 2025, 9:45 a.m. UTC 
  Suggested by Andrew Pinski. I think it makes sense to have it in here even
if perhaps a bit verbose, because we really try to tell bug reporters to
read the page properly.

This could also be a table.
---
 htdocs/bugs/index.html | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)

Comments

Sam James March 3, 2025, 10:15 a.m. UTC | #1 
Sam James <sam@gentoo.org> writes:

> Suggested by Andrew Pinski. I think it makes sense to have it in here even
> if perhaps a bit verbose, because we really try to tell bug reporters to
> read the page properly.
>
> This could also be a table.

Ping on this if I may.
Gerald Pfeifer March 3, 2025, 3:54 p.m. UTC | #2 
On Wed, 12 Feb 2025, Sam James wrote:
> Suggested by Andrew Pinski. I think it makes sense to have it in here 
> even if perhaps a bit verbose, because we really try to tell bug 
> reporters to read the page properly.

Makes sense.

> This could also be a table.

I'm not sure how a table would look like? (Genuinely, if you feel it'd be 
better happy to have a look.)

> +GCC maintains a 'Porting to' resource for new versions of the compiler:

How about skipping "of the compiler" (not the least since it's a set of 
compilers ;-) and then something like

  "...new version: GCC 15 | GCC 14 | GCC 13 | ..."

(or with commas or something along these lines)?

> +  <li><a href="https://gcc.gnu.org/gcc-15/porting_to.html">GCC 15</a></li>

Can you please make all these links relative, such as 
../gcc-15/porting_to.html ?

Fine with these changes. 

Can you please also enhance the documentation for our release managers?
Probably branching.html (over releasing HTML since some distros give new 
GCC versions a spin before the first release in the series).

Thank you,
Gerald
Sam James March 5, 2025, 11:11 p.m. UTC | #3 
Gerald Pfeifer <gerald@pfeifer.com> writes:

> On Wed, 12 Feb 2025, Sam James wrote:
>> Suggested by Andrew Pinski. I think it makes sense to have it in here 
>> even if perhaps a bit verbose, because we really try to tell bug 
>> reporters to read the page properly.
>
> Makes sense.
>
>> This could also be a table.
>
> I'm not sure how a table would look like? (Genuinely, if you feel it'd be 
> better happy to have a look.)

I wasn't sure if maybe a "long bulletpoint list" was an antipattern, and
then wondered about maybe "version/changes/porting to" as columns, but
on reflection, it's overkill and let's not worry about it.

>
>> +GCC maintains a 'Porting to' resource for new versions of the compiler:
>
> How about skipping "of the compiler" (not the least since it's a set of 
> compilers ;-) and then something like
>
>   "...new version: GCC 15 | GCC 14 | GCC 13 | ..."
>
> (or with commas or something along these lines)?

ACK.

>
>> +  <li><a href="https://gcc.gnu.org/gcc-15/porting_to.html">GCC 15</a></li>
>
> Can you please make all these links relative, such as 
> ../gcc-15/porting_to.html ?


ACK.

>
> Fine with these changes. 
>
> Can you please also enhance the documentation for our release managers?
> Probably branching.html (over releasing HTML since some distros give new 
> GCC versions a spin before the first release in the series).

Will do -- thank you for the helpful comments and the quick review!

>
> Thank you,
> Gerald

thanks,
sam
diff mbox series

Patch

diff --git a/htdocs/bugs/index.html b/htdocs/bugs/index.html
index 99d19095..910ed868 100644
--- a/htdocs/bugs/index.html
+++ b/htdocs/bugs/index.html
@@ -627,6 +627,30 @@  changed the parser rules so that <code>&lt;::</code> works as expected.
 
 <h3 id="upgrading">Common problems when upgrading the compiler</h3>
 
+<p>
+GCC maintains a 'Porting to' resource for new versions of the compiler:
+</p>
+<ul>
+  <li><a href="https://gcc.gnu.org/gcc-15/porting_to.html">GCC 15</a></li>
+  <li><a href="https://gcc.gnu.org/gcc-14/porting_to.html">GCC 14</a></li>
+  <li><a href="https://gcc.gnu.org/gcc-13/porting_to.html">GCC 13</a></li>
+  <li><a href="https://gcc.gnu.org/gcc-12/porting_to.html">GCC 12</a></li>
+  <li><a href="https://gcc.gnu.org/gcc-11/porting_to.html">GCC 11</a></li>
+  <li><a href="https://gcc.gnu.org/gcc-10/porting_to.html">GCC 10</a></li>
+  <li><a href="https://gcc.gnu.org/gcc-9/porting_to.html">GCC 9</a></li>
+  <li><a href="https://gcc.gnu.org/gcc-8/porting_to.html">GCC 8</a></li>
+  <li><a href="https://gcc.gnu.org/gcc-7/porting_to.html">GCC 7</a></li>
+  <li><a href="https://gcc.gnu.org/gcc-6/porting_to.html">GCC 6</a></li>
+  <li><a href="https://gcc.gnu.org/gcc-5/porting_to.html">GCC 5</a></li>
+  <li><a href="https://gcc.gnu.org/gcc-4.9/porting_to.html">GCC 4.9</a></li>
+  <li><a href="https://gcc.gnu.org/gcc-4.8/porting_to.html">GCC 4.8</a></li>
+  <li><a href="https://gcc.gnu.org/gcc-4.7/porting_to.html">GCC 4.7</a></li>
+  <li><a href="https://gcc.gnu.org/gcc-4.6/porting_to.html">GCC 4.6</a></li>
+  <!-- no such doc for 4.5 -->
+  <li><a href="https://gcc.gnu.org/gcc-4.4/porting_to.html">GCC 4.4</a></li>
+  <li><a href="https://gcc.gnu.org/gcc-4.3/porting_to.html">GCC 4.3</a></li>
+</ul>
+
 <h4>ABI changes</h4>
 
 <p>The C++ application binary interface (ABI) consists of two