Re: [PATCH v6] RISC-V:Optimize the MASK opt generation

[Gerald Pfeifer]

On Sun, 1 Oct 2023, Kito Cheng wrote:
> Committed to trunk, thanks Feng :)

Hmm, my nightly FreeBSD 12 tester now fails as follows:

  nawk -f /scratch/tmp/gerald/GCC-HEAD/gcc/opt-functions.awk \
-f /scratch/tmp/gerald/GCC-HEAD/gcc/opt-read.awk \
-f /scratch/tmp/gerald/GCC-HEAD/gcc/opth-gen.awk \
   < optionlist > tmp-options.h
  nawk: syntax error at source line 67 source file 
/scratch/tmp/gerald/GCC-HEAD/gcc/opt-read.awk
  context is
>>>other_masks[var_index][ 
<<< n_other_mask[var_index]++] = name
  nawk: illegal statement at source line 67 source file 
  /scratch/tmp/gerald/GCC-HEAD/gcc/opt-read.awk
  nawk -f /scratch/tmp/gerald/GCC-HEAD/gcc/opt-functions.awk \
-f /scratch/tmp/gerald/GCC-HEAD/gcc/opt-read.awk \
   -f /scratch/tmp/gerald/GCC-HEAD/gcc/optc-save-gen.awk \
   -v header_name="config.h system.h coretypes.h tm.h" < optionlist \
   > options-save.cc
  nawk: syntax error at source line 386 source file 
  /scratch/tmp/gerald/GCC-HEAD/gcc/opth-gen.awk
  nawk: syntax error at source line 67 source file 
  /scratch/tmp/gerald/GCC-HEAD/gcc/opt-read.awk
  context is
>>>other_masks[var_index][ 
<<< n_other_mask[var_index]++] = name
  nawk: illegal statement at source line 67 source file 
  /scratch/tmp/gerald/GCC-HEAD/gcc/opt-read.awk
  gmake[3]: *** [Makefile:2477: s-options-h] Error 2

Gerald

Re: [PATCH v6] RISC-V:Optimize the MASK opt generation

[Gerald Pfeifer]

On Mon, 2 Oct 2023, Kito Cheng wrote:
> Thanks for reporting this issue, I just realized multidimensional
> arrays are gawk extensions, could you try the attached patch to see if
> it can resolve the issue?

Yes, with that patch applied the build proceeds far beyond that point
(still running).

Thanks for the quick fix!

Gerald

Re: gcc-patches From rewriting mailman settings (Was: [Linaro-TCWG-CI] gcc patch #75674: FAIL: 68 regressions)

[Gerald Pfeifer]

On Tue, 19 Sep 2023, Mark Wielaard wrote:
>> Although there were some positive responses (on list and on irc) it is
>> sometimes hard to know if there really is consensus for these kind of
>> infrastructure tweaks. But I believe there is at least no sustained
>> opposition to changing the gcc-patches mailman setting as proposed
>> above.
> This change is now done for gcc-patches.

Yeah, yeah, yeah. Thank you!

>> And if there are no complaints at Cauldron we could do the same for
>> the other patch lists the week after.

Sadly I missed Cauldron - have there been any complaints there?

Can you adjust the g...@gcc.gnu.org list and others @gcc.gnu.org as well?
I for one would love to see that.

Thanks,
Gerald

[pushed] wwwdocs: conduct: Use instead of

[Gerald Pfeifer]

On the way break overly long lines.

Pushed.

Gerald
---
 htdocs/conduct-faq.html  | 3 ++-
 htdocs/conduct-report.html   | 3 ++-
 htdocs/conduct-response.html | 3 ++-
 htdocs/conduct.html  | 3 ++-
 4 files changed, 8 insertions(+), 4 deletions(-)

diff --git a/htdocs/conduct-faq.html b/htdocs/conduct-faq.html
index 380e9166..5b7a82a3 100644
--- a/htdocs/conduct-faq.html
+++ b/htdocs/conduct-faq.html
@@ -63,4 +63,5 @@ your question either,
 email mailto:cond...@gcc.gnu.org";>cond...@gcc.gnu.org with any
 additional questions or feedback.
 
-http://creativecommons.org/licenses/by-sa/4.0/";>https://i.creativecommons.org/l/by-sa/4.0/88x31.png"; />This work 
is licensed under a http://creativecommons.org/licenses/by-sa/4.0/";>Creative Commons 
Attribution-ShareAlike 4.0 International License.
+http://creativecommons.org/licenses/by-sa/4.0/";>https://i.creativecommons.org/l/by-sa/4.0/88x31.png"; />
+This work is licensed under a http://creativecommons.org/licenses/by-sa/4.0/";>Creative Commons 
Attribution-ShareAlike 4.0 International License.
diff --git a/htdocs/conduct-report.html b/htdocs/conduct-report.html
index 87758745..5f3fae90 100644
--- a/htdocs/conduct-report.html
+++ b/htdocs/conduct-report.html
@@ -113,7 +113,8 @@ directly to another member, or to a member of the Steering 
Committee.
 of the committee's decision. To make such a request, contact a member of the
 Steering Committee with your request and motivation.
 
-http://creativecommons.org/licenses/by-sa/4.0/";>https://i.creativecommons.org/l/by-sa/4.0/88x31.png"; />This work 
is licensed under a http://creativecommons.org/licenses/by-sa/4.0/";>Creative Commons 
Attribution-ShareAlike 4.0 International License.
+http://creativecommons.org/licenses/by-sa/4.0/";>https://i.creativecommons.org/l/by-sa/4.0/88x31.png"; />
+This work is licensed under a http://creativecommons.org/licenses/by-sa/4.0/";>Creative Commons 
Attribution-ShareAlike 4.0 International License.
 
 Text derived from
 the https://www.djangoproject.com/conduct/reporting/";>Django project
diff --git a/htdocs/conduct-response.html b/htdocs/conduct-response.html
index c67e8b0b..a25f6ae4 100644
--- a/htdocs/conduct-response.html
+++ b/htdocs/conduct-response.html
@@ -132,7 +132,8 @@ excluded from the response process. For these cases, anyone 
can make a report
 directly to any of the committee members, as documented in the reporting
 guidelines.
 
-http://creativecommons.org/licenses/by-sa/4.0/";>https://i.creativecommons.org/l/by-sa/4.0/88x31.png"; />This work 
is licensed under a http://creativecommons.org/licenses/by-sa/4.0/";>Creative Commons 
Attribution-ShareAlike 4.0 International License.
+http://creativecommons.org/licenses/by-sa/4.0/";>https://i.creativecommons.org/l/by-sa/4.0/88x31.png"; />
+This work is licensed under a http://creativecommons.org/licenses/by-sa/4.0/";>Creative Commons 
Attribution-ShareAlike 4.0 International License.
 
 Text derived from
 the https://www.djangoproject.com/conduct/enforcement-manual/";>Django
diff --git a/htdocs/conduct.html b/htdocs/conduct.html
index 736e2f6d..87bd01bf 100644
--- a/htdocs/conduct.html
+++ b/htdocs/conduct.html
@@ -114,7 +114,8 @@ email mailto:cond...@gcc.gnu.org";>cond...@gcc.gnu.org.
 that doesn't answer your questions, feel free
 to mailto:cond...@gcc.gnu.org";>contact us.
 
-http://creativecommons.org/licenses/by-sa/4.0/";>https://i.creativecommons.org/l/by-sa/4.0/88x31.png"; />This work 
is licensed under a http://creativecommons.org/licenses/by-sa/4.0/";>Creative Commons 
Attribution-ShareAlike 4.0 International License.
+http://creativecommons.org/licenses/by-sa/4.0/";>https://i.creativecommons.org/l/by-sa/4.0/88x31.png"; />
+This work is licensed under a http://creativecommons.org/licenses/by-sa/4.0/";>Creative Commons 
Attribution-ShareAlike 4.0 International License.
 
 Text derived from the https://www.djangoproject.com/conduct/";>Django
 project Code of Conduct, used under
-- 
2.42.0

[pushed] wwwdocs: conduct: Link creativecommons.org via https

[Gerald Pfeifer]

Browers are starting to complain about http links, and the server
actually redirects.

On the way break really long lines.

Pushed.
Gerald
---
 htdocs/conduct-faq.html  | 4 +++-
 htdocs/conduct-report.html   | 4 +++-
 htdocs/conduct-response.html | 4 +++-
 htdocs/conduct.html  | 4 +++-
 4 files changed, 12 insertions(+), 4 deletions(-)

diff --git a/htdocs/conduct-faq.html b/htdocs/conduct-faq.html
index 5b7a82a3..9ac65fbc 100644
--- a/htdocs/conduct-faq.html
+++ b/htdocs/conduct-faq.html
@@ -64,4 +64,6 @@ email mailto:cond...@gcc.gnu.org";>cond...@gcc.gnu.org with any
 additional questions or feedback.
 
 http://creativecommons.org/licenses/by-sa/4.0/";>https://i.creativecommons.org/l/by-sa/4.0/88x31.png"; />
-This work is licensed under a http://creativecommons.org/licenses/by-sa/4.0/";>Creative Commons 
Attribution-ShareAlike 4.0 International License.
+This work is licensed under a
+https://creativecommons.org/licenses/by-sa/4.0/";>
+Creative Commons Attribution-ShareAlike 4.0 International License.
diff --git a/htdocs/conduct-report.html b/htdocs/conduct-report.html
index 5f3fae90..58e4489e 100644
--- a/htdocs/conduct-report.html
+++ b/htdocs/conduct-report.html
@@ -114,7 +114,9 @@ of the committee's decision. To make such a request, 
contact a member of the
 Steering Committee with your request and motivation.
 
 http://creativecommons.org/licenses/by-sa/4.0/";>https://i.creativecommons.org/l/by-sa/4.0/88x31.png"; />
-This work is licensed under a http://creativecommons.org/licenses/by-sa/4.0/";>Creative Commons 
Attribution-ShareAlike 4.0 International License.
+This work is licensed under a
+https://creativecommons.org/licenses/by-sa/4.0/";>
+Creative Commons Attribution-ShareAlike 4.0 International License.
 
 Text derived from
 the https://www.djangoproject.com/conduct/reporting/";>Django project
diff --git a/htdocs/conduct-response.html b/htdocs/conduct-response.html
index a25f6ae4..a261554d 100644
--- a/htdocs/conduct-response.html
+++ b/htdocs/conduct-response.html
@@ -133,7 +133,9 @@ directly to any of the committee members, as documented in 
the reporting
 guidelines.
 
 http://creativecommons.org/licenses/by-sa/4.0/";>https://i.creativecommons.org/l/by-sa/4.0/88x31.png"; />
-This work is licensed under a http://creativecommons.org/licenses/by-sa/4.0/";>Creative Commons 
Attribution-ShareAlike 4.0 International License.
+This work is licensed under a
+https://creativecommons.org/licenses/by-sa/4.0/";>
+Creative Commons Attribution-ShareAlike 4.0 International License.
 
 Text derived from
 the https://www.djangoproject.com/conduct/enforcement-manual/";>Django
diff --git a/htdocs/conduct.html b/htdocs/conduct.html
index 87bd01bf..25790035 100644
--- a/htdocs/conduct.html
+++ b/htdocs/conduct.html
@@ -115,7 +115,9 @@ that doesn't answer your questions, feel free
 to mailto:cond...@gcc.gnu.org";>contact us.
 
 http://creativecommons.org/licenses/by-sa/4.0/";>https://i.creativecommons.org/l/by-sa/4.0/88x31.png"; />
-This work is licensed under a http://creativecommons.org/licenses/by-sa/4.0/";>Creative Commons 
Attribution-ShareAlike 4.0 International License.
+This work is licensed under a
+https://creativecommons.org/licenses/by-sa/4.0/";>
+Creative Commons Attribution-ShareAlike 4.0 International License.
 
 Text derived from the https://www.djangoproject.com/conduct/";>Django
 project Code of Conduct, used under
-- 
2.42.0

[pushed] wwwdocs: gcc-9: Editorial changes to porting_to.html

[Gerald Pfeifer]

Of course GCC 9 is not exactly fresh, though since I found this in a local 
tree still worth pushing.

Pushed.

Gerald
---
 htdocs/gcc-9/porting_to.html | 31 ---
 1 file changed, 16 insertions(+), 15 deletions(-)

diff --git a/htdocs/gcc-9/porting_to.html b/htdocs/gcc-9/porting_to.html
index 796c402e..fc85dae2 100644
--- a/htdocs/gcc-9/porting_to.html
+++ b/htdocs/gcc-9/porting_to.html
@@ -64,22 +64,23 @@ and provide solutions. Let us know if you have suggestions 
for improvements!
   that const qualified variables without mutable
   member are predetermined shared, but as an exception may be specified
   in the firstprivate clause.  OpenMP 4.0 dropped this rule,
-  but in the hope that the incompatible change will be reverted GCC kept
-  implementing the previous behavior.  Now that for OpenMP 5.0 it has been
+  but in the hope that this incompatible change will be reverted GCC kept
+  the previous behavior.  Now that for OpenMP 5.0 it has been
   confirmed this is not going to change, GCC 9 started implementing the
-  OpenMP 4.0 and later behavior.  When not using default
+  OpenMP 4.0 and later behavior.  When not using a default
   clause or when using default(shared), this makes no
-  difference, but if using default(none), previously the
-  choice was not specify the const qualified variables
-  on the construct at all, or specify in firstprivate clause.
-  In GCC 9 as well as for OpenMP 4.0 compliance, those variables need
-  to be specified on constructs in which they are used, either in
-  shared or in firstprivate clause.  Specifying
-  them in firstprivate clause is one way to achieve
-  compatibility with both older GCC versions and GCC 9, another option
+  difference. When using default(none), previously the
+  choice was not to specify const qualified variables
+  on the construct at all, or specify them in the
+  firstprivate clause.
+  In GCC 9 as well as for OpenMP 4.0 compliance those variables need
+  to be specified on constructs in which they are used, either in a
+  shared or in a firstprivate clause.  Specifying
+  them in a firstprivate clause is one way to achieve
+  compatibility with both older GCC versions and GCC 9. Another option
   is to drop the default(none) clause.  In C++,
   const variables with constant initializers which are not
-  odr-used in the region, but replaced with their constant initializer
+  odr-used in the region, but replaced with their constant initializer,
   are not considered to be referenced in the region for
   default(none) purposes.
 
@@ -93,8 +94,8 @@ and provide solutions. Let us know if you have suggestions 
for improvements!
 for (int i = 0; i < a; i += b)
   ;
 // The above used to compile with GCC 8 and older, but will
-// not anymore with GCC 9.  firstprivate(a, b) clause needs
-// to be added for C, for C++ it could be just firstprivate(a)
+// not anymore with GCC 9. A firstprivate(a, b) clause needs
+// to be added for C; for C++ it could be just firstprivate(a)
 // to make it compatible with all GCC releases.
   }
   const int huge_array[1024] wwwdocs: = { ... };
@@ -104,7 +105,7 @@ and provide solutions. Let us know if you have suggestions 
for improvements!
   use (huge_array[i] wwwdocs:);
 // Similarly, this used to compile with GCC 8 and older and
 // will not anymore.  Adding firstprivate(huge_array) is
-// probably undesirable here, so, either
+// probably undesirable here, so either
 // default(none) shared(huge_array) should be used and it will
 // only support GCC 9 and later, or default(none) should be
 // removed and then it will be compatible with all GCC releases
-- 
2.42.0

[pushed] wwwdocs: *: Remove unused buildstat pages

[Gerald Pfeifer]

[ Release managers, heads-up for when you branch future releases! ]

For GCC 9 to GCC 13 the per-release series buildstat pages have not
been populated at all, so remove them and reference from the respective
main release pages.

Pushed.
Gerald
---
 htdocs/gcc-10/buildstat.html | 27 ---
 htdocs/gcc-10/index.html |  3 ---
 htdocs/gcc-11/buildstat.html | 27 ---
 htdocs/gcc-11/index.html |  3 ---
 htdocs/gcc-12/buildstat.html | 27 ---
 htdocs/gcc-12/index.html |  3 ---
 htdocs/gcc-13/buildstat.html | 27 ---
 htdocs/gcc-13/index.html |  3 ---
 htdocs/gcc-9/buildstat.html  | 27 ---
 htdocs/gcc-9/index.html  |  3 ---
 10 files changed, 150 deletions(-)
 delete mode 100644 htdocs/gcc-10/buildstat.html
 delete mode 100644 htdocs/gcc-11/buildstat.html
 delete mode 100644 htdocs/gcc-12/buildstat.html
 delete mode 100644 htdocs/gcc-13/buildstat.html
 delete mode 100644 htdocs/gcc-9/buildstat.html

diff --git a/htdocs/gcc-10/buildstat.html b/htdocs/gcc-10/buildstat.html
deleted file mode 100644
index 5d18742e..
--- a/htdocs/gcc-10/buildstat.html
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
-
-
-Build status for GCC 10
-https://gcc.gnu.org/gcc.css";>
-
-
-
-Build status for GCC 10
-
-This list summarizes build reports for GCC 10.x, with links to the
-archived mail messages that reported the builds and to test result
-summaries.
-
-Instructions for running the test suite and for submitting test results
-are part of
-http://gcc.gnu.org/install/test.html";>
-Installing GCC: Testing.
-Instructions for reporting a successful "make bootstrap",
-including a list of information to include in such a report, are part of
-http://gcc.gnu.org/install/finalinstall.html";>
-Installing GCC: Final Installation.
-
-
-
diff --git a/htdocs/gcc-10/index.html b/htdocs/gcc-10/index.html
index a9547d18..5fb1e02e 100644
--- a/htdocs/gcc-10/index.html
+++ b/htdocs/gcc-10/index.html
@@ -63,9 +63,6 @@ GCC 10.4 relative to previous releases of GCC.
 supports several other languages aside from C, it now stands for the
 GNU Compiler Collection.
 
-A list of successful builds is updated
-as new information becomes available.
-
 The GCC developers would like to thank the numerous people that have
 contributed new features, improvements, bug fixes, and other changes as
 well as test results to GCC.
diff --git a/htdocs/gcc-11/buildstat.html b/htdocs/gcc-11/buildstat.html
deleted file mode 100644
index c86238c6..
--- a/htdocs/gcc-11/buildstat.html
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
-
-
-Build status for GCC 11
-https://gcc.gnu.org/gcc.css";>
-
-
-
-Build status for GCC 11
-
-This list summarizes build reports for GCC 11.x, with links to the
-archived mail messages that reported the builds and to test result
-summaries.
-
-Instructions for running the test suite and for submitting test results
-are part of
-http://gcc.gnu.org/install/test.html";>
-Installing GCC: Testing.
-Instructions for reporting a successful "make bootstrap",
-including a list of information to include in such a report, are part of
-http://gcc.gnu.org/install/finalinstall.html";>
-Installing GCC: Final Installation.
-
-
-
diff --git a/htdocs/gcc-11/index.html b/htdocs/gcc-11/index.html
index 7cd96f7e..bb41c492 100644
--- a/htdocs/gcc-11/index.html
+++ b/htdocs/gcc-11/index.html
@@ -54,9 +54,6 @@ GCC 11.3 relative to previous releases of GCC.
 supports several other languages aside from C, it now stands for the
 GNU Compiler Collection.
 
-A list of successful builds is updated
-as new information becomes available.
-
 The GCC developers would like to thank the numerous people that have
 contributed new features, improvements, bug fixes, and other changes as
 well as test results to GCC.
diff --git a/htdocs/gcc-12/buildstat.html b/htdocs/gcc-12/buildstat.html
deleted file mode 100644
index e066026f..
--- a/htdocs/gcc-12/buildstat.html
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
-
-
-Build status for GCC 12
-https://gcc.gnu.org/gcc.css";>
-
-
-
-Build status for GCC 12
-
-This list summarizes build reports for GCC 12.x, with links to the
-archived mail messages that reported the builds and to test result
-summaries.
-
-Instructions for running the test suite and for submitting test results
-are part of
-http://gcc.gnu.org/install/test.html";>
-Installing GCC: Testing.
-Instructions for reporting a successful "make bootstrap",
-including a list of information to include in such a report, are part of
-http://gcc.gnu.org/install/finalinstall.html";>
-Installing GCC: Final Installation.
-
-
-
diff --git a/htdocs/gcc-12/index.html b/htdocs/gcc-12/index.html
index f8c589e8..a76ef1dc 100644
--- a/htdocs/gcc-12/index.html
+++ b/htdocs/gcc-12/index.html
@@ -48,9 +48,6 @@ GCC 12.2 relative to previous releases of GCC.
 supports several other languages aside from C, it now stands for the
 GNU Compiler Collection.
 
-A list of successful builds is up

[pushed] wwwdocs: buildstat: Don't reference buildstats we no longer carry

[Gerald Pfeifer]

Having just removed the buildstats pages for GCC 9 to GCC 13 also
drop references from this main buildstats overview.

Pushed.

Gerald
---
 htdocs/buildstat.html | 8 ++--
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/htdocs/buildstat.html b/htdocs/buildstat.html
index cb27a979..08c9c2b7 100644
--- a/htdocs/buildstat.html
+++ b/htdocs/buildstat.html
@@ -10,14 +10,10 @@
 
 Build status for GCC
 
-These pages summarize build reports for GCC.
+These pages summarize build reports we gathered for older releases
+of GCC.
 
 
-GCC 13.x
-GCC 12.x
-GCC 11.x
-GCC 10.x
-GCC 9.x
 GCC 8.x
 GCC 7.x
 GCC 6.x
-- 
2.42.0

Re: [PATCH][wwwdocs] Mention Cortex-A76 support in GCC 9 changes.html

[Gerald Pfeifer]

On Fri, 29 Jun 2018, Kyrill  Tkachov wrote:
> This patch adds support for the Arm Cortex-A76 processor in changes.html 
> for GCC 9. It enables the AArch64 section of the page and adds the news 
> blob there. It also adds an entry to the already-existing arm entry.

Thank you, Kyrill.

Should I also apply the change below to account for the recent
ARM to Arm rebranding?

Gerald

Index: changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-9/changes.html,v
retrieving revision 1.12
diff -u -r1.12 changes.html
--- changes.html4 Jul 2018 20:22:12 -   1.12
+++ changes.html12 Jul 2018 23:25:41 -
@@ -99,7 +99,7 @@
 
 
 
-ARM
+Arm
 
   
 Support has been added for the following processors

Re: [PATCH] x86: Tune Skylake, Cannonlake and Icelake as Haswell

[Gerald Pfeifer]

On Fri, 13 Jul 2018, H.J. Lu wrote:
> I will do the same for GCC8 backport.

Can you please add a note to gcc-8/changes.html?  This seems big
enough to warrant a note in a part for GCC 8.2.

(At gcc-7/changes.html you can see how to go about this for minor
releases.)

Gerald

[wwwdocs] extensions.html - remove "rogue" MELT page

[Gerald Pfeifer]

I noticed that http://gcc-melt.org now redirects to
http://www.gcc-melt.org which looks like a default,
and empty, Wordpress installation.

I went ahead and applied the patch below.

Basile, should we generally remove this reference to GCC MELT?

Gerald

Index: extensions.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/extensions.html,v
retrieving revision 1.59
diff -u -r1.59 extensions.html
--- extensions.html 2 Jun 2018 21:16:09 -   1.59
+++ extensions.html 14 Jul 2018 20:14:45 -
@@ -21,7 +21,7 @@
 analysis, debugging, and performance tuning in concurrent code.
 
 
-http://gcc-melt.org";>GCC MELT
+GCC MELT
 
 MELT is a high-level domain specific language to ease the
   development of GCC extensions. It is available as a GCC experimental

[wwwdocs] gcc-4.3/changes.html - switch www.mpfr.org to https

[Gerald Pfeifer]

Applied.

Gerald

Index: gcc-4.3/changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.3/changes.html,v
retrieving revision 1.133
diff -u -r1.133 changes.html
--- gcc-4.3/changes.html2 Jun 2018 21:16:16 -   1.133
+++ gcc-4.3/changes.html14 Jul 2018 21:01:20 -
@@ -21,7 +21,7 @@
   
 GCC requires the https://gmplib.org/";>GMP and http://www.mpfr.org/";>MPFR libraries for building all
+href="https://www.mpfr.org";>MPFR libraries for building all
 the various front-end languages it supports.  See the https://gcc.gnu.org/install/prerequisites.html";>prerequisites
 page for version requirements.

[wwwdocs] adjust www.itl.nist.gov to https in readings.html

[Gerald Pfeifer]

Applied.

Gerald

Index: readings.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,v
retrieving revision 1.294
diff -u -r1.294 readings.html
--- readings.html   2 Jun 2018 21:16:10 -   1.294
+++ readings.html   14 Jul 2018 21:31:53 -
@@ -414,9 +414,9 @@
   Some packages aimed at Fortran compiler validation.
 
   
-http://www.itl.nist.gov/div897/ctg/fortran_form.htm";>FORTRAN
+https://www.itl.nist.gov/div897/ctg/fortran_form.htm";>FORTRAN
 77 test suite by the NIST Information Technology Laboratory
-(http://www.itl.nist.gov/div897/ctg/software.htm";>license)
+(https://www.itl.nist.gov/div897/ctg/software.htm";>license)
 contains legal and operational Fortran 77 code.
   
   

[wwwdocs] Adjust a link to microsoft.com in gcc-4.7/changes.html

[Gerald Pfeifer]

Applied.

Gerald

Index: gcc-4.7/changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.7/changes.html,v
retrieving revision 1.148
diff -u -r1.148 changes.html
--- gcc-4.7/changes.html2 Jun 2018 21:16:17 -   1.148
+++ gcc-4.7/changes.html15 Jul 2018 05:54:58 -
@@ -636,7 +636,7 @@
   depends on the user environment settings; see the ulimit -c
   setting for POSIX shells, limit coredumpsize for C shells,
   and the https://msdn.microsoft.com/en-us/library/bb787181%28v=vs.85%29.aspx";
+  
href="https://docs.microsoft.com/en-us/windows/desktop/wer/collecting-user-mode-dumps";
   >WER user-mode dumps settings on Windows.
 The https://gcc.gnu.org/onlinedocs/gcc-4.7.1/gfortran/Debugging-Options.html#index-g_t_0040code_007bfno_002dbacktrace_007d-183";

Re: [PATCH] x86: Tune Skylake, Cannonlake and Icelake as Haswell

[Gerald Pfeifer]

On Sat, 14 Jul 2018, H.J. Lu wrote:
> Like this?

Yes, this looks fine.

Thanks!
Gerald

Re: [wwwdocs] Document new sve-acle-branch

[Gerald Pfeifer]

On Wed, 18 Jul 2018, Richard Sandiford wrote:
> I've created a new git branch for developing the SVE ACLE (i.e. 
> intrinsics) implementation.  Is the branches entry below OK to commit?  

Yes, thanks you!

(Perhaps ChangeLogs instead of changelogs, but I leave this to you.)

> Although the branch is on git rather than svn, other git branches have 
> also been documented here.

Makes sense.  We probably should (once out of CVS, ahem) rename
that page or split of the part covering the branches.

Gerald

Re: [wwwdocs] Mention LTO link-time issue fixed in gcc 8.2

[Gerald Pfeifer]

On Thu, 19 Jul 2018, Jan Hubicka wrote:
> since we now mention the problem with Intel tuning, I tought we also may 
> mention the LTO link-time issue that was fixed.  It was mentioned by 
> several folks at the phoronix forum. (Basicaly sometimes the partition 
> size has overlfown which made partitioner to put every symbol into 
> separate parition causing fork bomb while streaming and overall very 
> slow compile times).

Thanks, Jan, this looks fine to me.

Gerald

Re: [wwwdocs] Mention LTO link-time issue fixed in gcc 8.2

[Gerald Pfeifer]

On Sat, 21 Jul 2018, Gerald Pfeifer wrote:
> Thanks, Jan, this looks fine to me.

Oops, I missed  closing an ; just followed up on your
commit to fix that.

Gerald

Index: changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-8/changes.html,v
retrieving revision 1.90
diff -u -r1.90 changes.html
--- changes.html21 Jul 2018 19:55:10 -  1.90
+++ changes.html22 Jul 2018 08:25:46 -
@@ -1321,7 +1321,7 @@
 complete (that is, it is possible that some PRs that have been fixed
 are not listed here).
 
-General Improvements
+General Improvements
   
 Fixed LTO link-time performance problems caused by an overflow
in the partitioning algorithm while building large binaries.

Re: [PATCH 1/4] Clean up of new format of -falign-FOO.

[Gerald Pfeifer]

On Wed, 18 Jul 2018, Martin Sebor wrote:
> I'm seeing lots of warnings for this file:
> 
> /ssd/src/gcc/svn/gcc/align.h:53:32: warning: extended initializer lists only
> available with -std=c++11 or -std=gnu++11

With clang version 3.4 (system compiler on FreeBSD 10.x) this is
even a hard error and GCC failed to build.  So thanks for fixing
this, Martin!

Gerald

Re: [PATCH 8/8] Enhance documentation of gcov.

[Gerald Pfeifer]

On Fri, 28 Apr 2017, Martin Sebor wrote:
>> 2017-04-27  Martin Liska  
>>
>>  * doc/gcov.texi: Enhance documentation of gcov.
> Since I started picking on this change set I might as well keep
> at it ;)   Just a tiny nit: the sentence is missing a preposition:
> 
>   depending on  whether a basic block is reachable.

This adds a bit more.  Applied.

(This section still needs a bit more love, ideally by a native
speaker.)

Gerald


2018-07-22  Gerald Pfeifer  

* doc/gcov.texi (Invoking Gcov): Editorial changes.

Index: doc/gcov.texi
===
--- doc/gcov.texi   (revision 262161)
+++ doc/gcov.texi   (working copy)
@@ -378,12 +378,12 @@
 containing no code.  Unexecuted lines are marked @samp{#} or
 @samp{=}, depending on whether they are reachable by
 non-exceptional paths or only exceptional paths such as C++ exception
-handlers, respectively. Given @samp{-a} option, unexecuted blocks are
+handlers, respectively. Given the @samp{-a} option, unexecuted blocks are
 marked @samp{$} or @samp{%}, depending on whether a basic block
 is reachable via non-exceptional or exceptional paths.
 Executed basic blocks having a statement with zero @var{execution_count}
-end with @samp{*} character and are colored with magenta color with @option{-k}
-option.  The functionality is not supported in Ada.
+end with @samp{*} character and are colored with magenta color with
+the @option{-k} option.  This functionality is not supported in Ada.
 
 Note that GCC can completely remove the bodies of functions that are
 not needed -- for instance if they are inlined everywhere.  Such functions

Re: [PATCH 1/4] Clean up of new format of -falign-FOO.

[Gerald Pfeifer]

On Sun, 22 Jul 2018, Gerald Pfeifer wrote:
> With clang version 3.4 (system compiler on FreeBSD 10.x) this is
> even a hard error and GCC failed to build.  So thanks for fixing
> this, Martin!

Unfortunately it appears there was another bootstrap failure hidden
behind that one:


In file included from /scratch/tmp/gerald/GCC-HEAD/gcc/system.h:691,
 from /scratch/tmp/gerald/GCC-HEAD/gcc/tree-vect-slp.c:23:
/scratch/tmp/gerald/GCC-HEAD/gcc/tree-vect-slp.c: In function 
‘_slp_tree* vect_build_slp_tree_2(vec_info*, vec, unsigned int, 
poly_uint64*, vec<_slp_tree*>*, bool*, unsigned int*, unsigned int*, 
unsigned int)’:
/scratch/tmp/gerald/GCC-HEAD/gcc/../include/libiberty.h:722:36: error: ‘alloca’ 
bound is unknown [-Werror=alloca-larger-than=]
 # define alloca(x) __builtin_alloca(x)
^~~
/scratch/tmp/gerald/GCC-HEAD/gcc/../include/libiberty.h:356:33: note: in 
expansion of macro ‘alloca’
 #define XALLOCAVEC(T, N) ((T *) alloca (sizeof (T) * (N)))
 ^~
/scratch/tmp/gerald/GCC-HEAD/gcc/tree-vect-slp.c:1437:16: note: in expansion of 
macro ‘XALLOCAVEC’
bool *tem = XALLOCAVEC (bool, group_size);
^~
cc1plus: all warnings being treated as errors
gmake[3]: *** [Makefile:1112: tree-vect-slp.o] Error 1
gmake[3]: Leaving directory '/scratch/tmp/gerald/OBJ-0722-0939/gcc'
gmake[2]: *** [Makefile:4644: all-stage2-gcc] Error 2


This is on FreeBSD 10.4 which features clang 3.4.1 as system compiler;
FreeBSD 11.2 with clang 6.0.0 does not trigger that.

Gerald

[wwwdocs] Replace by id= attributes in all of projects/

[Gerald Pfeifer]

...and avoid a few that weren't referenced.

This is the next step in cleaning up and simplifying our pages for
a transition to the (simpler) HTML 5.

Applied; and below a follow-up patch since a few idosyncracies
escaped my own verification.

Gerald

Index: projects/ast-optimizer.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/ast-optimizer.html,v
retrieving revision 1.10
diff -u -r1.10 ast-optimizer.html
--- projects/ast-optimizer.html 2 Jun 2018 21:16:20 -   1.10
+++ projects/ast-optimizer.html 12 Jul 2018 23:26:41 -
@@ -91,7 +91,7 @@
 See https://gcc.gnu.org/ml/gcc-patches/2001-07/msg00859.html";>this
 thread.
 
-SSA for trees
+SSA for trees
 
 The tree SSA infrastructure is maintained by mailto:dnovi...@redhat.com";>Diego Novillo
Index: projects/cfg.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/cfg.html,v
retrieving revision 1.25
diff -u -r1.25 cfg.html
--- projects/cfg.html   2 Jun 2018 21:16:20 -   1.25
+++ projects/cfg.html   12 Jul 2018 23:26:42 -
@@ -114,7 +114,7 @@
 algorithms and keep code size under control.  The purpose of this pass
 is to minimize the number of branches and cache misses.  It uses code
 duplication to avoid jumps.  A trivial example is copying the return
-instruction instead of jumping to it.  See [6] for a
+instruction instead of jumping to it.  See [6] for a
 detailed description.
 
 Implementation in GCC
@@ -356,7 +356,7 @@
 Implementation in GCC
 
 We plan to do loop peeling and superblock formation in single pass
-as described in [3].
+as described in [3].
  
 Enhancements that are currently only in the cfg-branch:
 
@@ -404,7 +404,7 @@
 look like a real file format.
 
 There are a few references to much more advanced profiling systems
-in [3].
+in [3].
 
 This is done using NOTE_INSN_PREDICTION emitted in the
 stream converted to REG_PREDICTION later.  For instance,
@@ -450,55 +450,55 @@
 homepage. Some other papers:
 
 
-[1]
+[1]
 
 https://doi.org/10.1145/155090.155119";>Branch
 Prediction for Free; Ball and Larus; PLDI '93.
 
-[2]
+[2]
 
 https://doi.org/10.1145/192724.192725";>Static
 Branch Frequency and Program Profile Analysis; Wu and Larus;
 MICRO-27.
 
-[3]
+[3]
 
 Design and Analysis of Profile-Based Optimization in Compaq's
 Compilation Tools for Alpha; Journal of Instruction-Level Parallelism 3
 (2000) 1-25.
 
-[4]
+[4]
 
 http://www.lighterra.com/papers/valuerangeprop/Patterson1995-ValueRangeProp.pdf";>Accurate
 Static Branch Prediction by Value Range Propagation; Jason R. C.
 Patterson (jas...@fit.qut.edu.au), 1995
 
-[5]
+[5]
 
 https://doi.org/10.1145/258916.258932";>Near-optimal
 Intraprocedural Branch Alignment; Cliff Young, David S. Johnson,
 David R. Karger, Michael D. Smith, ACM 1997
 
-[6]
+[6]
 
 https://doi.org/10.1145/305138.305178";>Software
 Trace Cache; International Conference on Supercomputing, 1999
 
-[7]
+[7]
 
 https://doi.org/10.1002/spe.4380211204";>Using
 Profile Information to Assist Classic Code Optimizations; Pohua P.
 Chang, Scott A. Mahlke, and Wen-mei W. Hwu, 1991
 
-[8]
+[8]
 
 http://citeseer.ist.psu.edu/viewdoc/summary?doi=10.1.1.39.1922";>Hyperblock
 Performance Optimizations For ILP Processors; David Isaac August,
 1996 (Master Thesis)
 
-[9]
+[9]
 
 https://doi.org/10.1145/173262.155118";>Reverse
 If-Conversion; Nancy J. Warter, Scott A. Mahlke, Wen-mei W. Hwu, B.
Index: projects/cfo.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/cfo.html,v
retrieving revision 1.11
diff -u -r1.11 cfo.html
--- projects/cfo.html   2 Jun 2018 21:16:20 -   1.11
+++ projects/cfo.html   12 Jul 2018 23:26:42 -
@@ -19,7 +19,7 @@
 To do
 
 
-Latest News
+Latest News
 
 
 2005-08-11
@@ -33,7 +33,7 @@
 
 
 
-Introduction
+Introduction
 
 Code factoring is the name of a class of useful optimization techniques 
 developed especially for code size reduction. These approaches aim to reduce
@@ -43,7 +43,7 @@
 size optimization of GCC with code factoring methods (code motion and merging
 algorithms). The implementation currently resides on the branch.
 
-Contributing
+Contributing
 
 Checkout the cfo-branch branch from
 our respository.
@@ -52,7 +52,7 @@
 [cfo] in the subject. The usual contribution and testing rules apply. This
 branch is maintained by mailto:l...@gcc.gnu.org";>Gabor Loki.
 
-Documentation
+Documentation
 
 The project includes the following two code factoring algorithms:
 
@@ -146,7 +146,7 @@
 ftp://gcc.gnu.org/pub/gcc/summit/2004/Code%20Factoring.pdf";>
 GCC Summit Proceedings (2004).
 
-Features
+Features
 
 Currently the following algorithms are implemented on the branch:
 
@@ -157,7 +157,7 @@
 Sequence abstraction on Tree (-ftree-seqabstr)
 
 
-Preliminary results
+Preliminary results
 
 The following results have been prepared using the 
 http://szeged.github.io/csibe/";>CSiBE benchmark with re

Re: front-page news rotation policy?

[Gerald Pfeifer]

Hi Sandra,

On Sun, 29 Jul 2018, Sandra Loosemore wrote:
> Gerald, do we have a policy on when to rotate the News items on the main 
> GCC web page to the "Older news" page?  Joseph asked me to post a patch 
> for adding a news item for the proposed new C-SKY port, but the items 
> that are there now seem somewhat bit-rotten (e.g., referring to last 
> year's Cauldron in the future tense and no link for this year's event) 

that is a good question and also a fair observation that I've fallen
behind on rotating the news recently.

Let me try to address two birds with one stone, by means of the patch
below which (a) adds a note on rotating news to index.html and (b) does
a bit of rotation, and which I just applied.

Hope this makes sense and addresses your question?  

(Modulo my typo.)

> independently of anything to do with C-SKY.  Of course I can fix that 
> too (with a separate patch), given some hint about whether/how much 
> pruning is considered appropriate.

That would be lovely, thank you!

Gerald


Index: index.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/index.html,v
retrieving revision 1.1088
diff -u -r1.1088 index.html
--- index.html  26 Jul 2018 10:40:16 -  1.1088
+++ index.html  29 Jul 2018 22:23:29 -
@@ -43,6 +43,11 @@
 
 
 
+
+
 
 News
 
@@ -79,33 +84,6 @@
 [2017-05-24]
 ...instead of bzip2.
 
-GCC 7.1 released
-[2017-05-02]
-
-
-GNU Toolchain Fund
- [2017-03-09]
- A fund under the auspices of the Free Software Foundation 
specifically to benefit the components of the GNU Toolchain (GCC, GDB, GLIBC, 
Binutils, etc.) now https://www.fsf.org/news/gnu-toolchain-now-accepting-donations-with-the-support-of-the-free-software-foundation";>accepting
 donations.
-
-RISC-V support
- [2017-02-02]
- Support for the https://riscv.org";>RISC-V ISA was added, 
contributed by Palmer Dabbelt and Andrew Waterman.
-
-BRIG/HSAIL (Heterogeneous Systems Architecture Intermediate 
Language) front end added
- [2017-02-01]
- http://www.hsafoundation.com/";> Heterogeneous Systems
- Architecture 1.0 BRIG (HSAIL)
- front end was added to GCC,
- enabling HSAIL finalization for gcc-supported
- targets. The code was developed by
- http://parmance.com";>Parmance with sponsorship from
- https://www.generalprocessortech.com";>General Processor 
Technologies.
-
-Fuchsia OS support
- [2017-01-10]
- https://fuchsia.googlesource.com/";>Fuchsia OS
- support was added to GCC, contributed by Google.
-
 
 
 
Index: news.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/news.html,v
retrieving revision 1.161
diff -u -r1.161 news.html
--- news.html   2 Jun 2018 21:16:10 -   1.161
+++ news.html   29 Jul 2018 22:23:29 -
@@ -15,6 +15,33 @@
 
 
 
+GCC 7.1 released
+[2017-05-02]
+
+
+GNU Toolchain Fund
+ [2017-03-09]
+ A fund under the auspices of the Free Software Foundation 
specifically to benefit the components of the GNU Toolchain (GCC, GDB, GLIBC, 
Binutils, etc.) now https://www.fsf.org/news/gnu-toolchain-now-accepting-donations-with-the-support-of-the-free-software-foundation";>accepting
 donations.
+
+RISC-V support
+ [2017-02-02]
+ Support for the https://riscv.org";>RISC-V ISA was added, 
contributed by Palmer Dabbelt and Andrew Waterman.
+
+BRIG/HSAIL (Heterogeneous Systems Architecture Intermediate 
Language) front end added
+ [2017-02-01]
+ http://www.hsafoundation.com/";> Heterogeneous Systems
+ Architecture 1.0 BRIG (HSAIL)
+ front end was added to GCC,
+ enabling HSAIL finalization for gcc-supported
+ targets. The code was developed by
+ http://parmance.com";>Parmance with sponsorship from
+ https://www.generalprocessortech.com";>General Processor 
Technologies.
+
+Fuchsia OS support
+ [2017-01-10]
+ https://fuchsia.googlesource.com/";>Fuchsia OS
+ support was added to GCC, contributed by Google.
+
 GCC 6.3 released
 [2016-12-21]
 

[pushed] wwwdocs: gcc-4.5: Update link to GNU MPC

[Gerald Pfeifer]

---
 htdocs/gcc-4.5/changes.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/htdocs/gcc-4.5/changes.html b/htdocs/gcc-4.5/changes.html
index 2e8f56a7..3d645bb3 100644
--- a/htdocs/gcc-4.5/changes.html
+++ b/htdocs/gcc-4.5/changes.html
@@ -18,7 +18,7 @@
 
   
 GCC now requires the https://www.multiprecision.org/mpc/";>MPC library in order to
+href="https://www.multiprecision.org";>MPC library in order to
 build.  See the https://gcc.gnu.org/install/prerequisites.html";>prerequisites
 page for version requirements.
-- 
2.41.0

Re: [PATCH][wwwdocs] gcc-12/changes.html: document LoongArch -m{no-,}check-zero-division default change for 12.2

[Gerald Pfeifer]

On Mon, 4 Jul 2022, Xi Ruoyao wrote:
> Document a behavior change in r12-8546.  Ok for wwwdocs?

Thanks also for including the GCC 12.2 bug query as part of this. :)

Gerald

Re: [PATCH][wwwdocs] gcc-13: Add loongarch '-mexplicit-relocs' support

[Gerald Pfeifer]

On Tue, 26 Jul 2022, Lulu Cheng wrote:
> +LoongArch
> +
> +  The option -mexplicit-relocs has been added, this 
> indicates
> +  whether the la.* macro instructions will be generated when
> +  loading symbolic addresses.

How about making this "...has been added. It indicates..." or, if you
prefer one sentence "...has been added to indicate whether"?

> +  This feature requires binutils version 2.40 or later. If you want to use 
> the
> +  older version of bintuils, add compiler parameters
> +  -mno-explicit-relocs at compile time.

"...older versions..." (or "...an older version...")

And I believe we can simplify and just say "...add -mno-explicit..."

> +  The method for calling global functions changed from
> +  la.global + jirl to bl when complied add
> +  -fplt.

Do you mean "compiled" instead of "complied"?

And maybe "compiled with"?

> +  Enable option -fsection-anchors when -O1 and
> +  more advanced optimization.

How about "-fsection-anchors is now enabled with 
-O1 and above"?


If my suggestions make sense to you, please go ahead and commit with those
or variations thereof you may prefer. 

If you have any questions, please let me know and we'll sort things out
quickly.

Thank you,
Gerald

[committed] wwwdocs: cxx-status: Move www.open-std.org to https

[Gerald Pfeifer]

This is a trivial change which fixes several dozen links.

Marek, Jason, Jonathan - I noticed that (in other places) we have both 
links to www.open-std.org and open-std.org, both of which seem to work.

What is the preferred spelling of that site? With or without www? (The
latter would be shorter and sweeter. ;-)

Gerald
---
 htdocs/projects/cxx-status.html | 182 
 1 file changed, 91 insertions(+), 91 deletions(-)

diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html
index 18fb6408..ae0321c0 100644
--- a/htdocs/projects/cxx-status.html
+++ b/htdocs/projects/cxx-status.html
@@ -852,25 +852,25 @@
 
 
Removing trigraphs 
-  http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4086.html";>N4086
 
+  https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4086.html";>N4086
 
5 

 
 
   u8 character literals 
-  http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4267.html";>N4267
 
+  https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4267.html";>N4267
 
6 
__cpp_unicode_characters >= 201411 
 
 
Folding expressions
-  http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4295.html";>N4295
 
+  https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4295.html";>N4295
 
6 
__cpp_fold_expressions >= 201411
 
 
Attributes for namespaces and enumerators 
-  http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4266.html";>N4266
 
+  https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4266.html";>N4266
 
4.9 
(namespaces) 
 6 (enumerators) 
   
@@ -880,43 +880,43 @@
 
 
Nested namespace definitions
-  http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4230.html";>N4230
 
+  https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4230.html";>N4230
 
6 
__cpp_nested_namespace_definitions >= 201411
 
 
Allow constant evaluation for all non-type template arguments
-  http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4268.html";>N4268
 
+  https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4268.html";>N4268
 
6 
   __cpp_nontype_template_args >= 201411 
 
 
Extending static_assert 
-  http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n3928.pdf";>N3928
 
+  https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n3928.pdf";>N3928
 
   6
__cpp_static_assert >= 201411 
 
 
   New Rules for auto deduction from braced-init-list
-  http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n3922.html";>N3922
 
+  https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n3922.html";>N3922
 
   5
   
 
 
   Allow typename in a template template parameter
-  http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4051.html";>N4051
 
+  https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4051.html";>N4051
 
   5
   
 
 
[[fallthrough] wwwdocs:] attribute 
-  http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0188r1.pdf";>P0188R1
+  https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0188r1.pdf";>P0188R1
   7
__has_cpp_attribute(fallthrough)
 
 
[[nodiscard] wwwdocs:] attribute
-  http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0189r1.pdf";>P0189R1
+  https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0189r1.pdf";>P0189R1
   
4.8 
([[gnu::warn_unused_result] wwwdocs:])
7 (P0189R1)
@@ -924,7 +924,7 @@
 
 
[[maybe_unused] wwwdocs:] attribute
-  http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0212r1.pdf";>P0212R1
+  https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0212r1.pdf";>P0212R1
   
4.8 ([[gnu::unused] 
wwwdocs:])
 7 (P0212R1)
@@ -932,44 +932,44 @@
 
 
Extension to aggregate initialization
-  http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/p0017r1.html";>P0017R1
+  https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/p0017r1.html";>P0017R1
   7
__cpp_aggregate_bases >= 201603
 
 
Wording for constexpr lambda 
-  http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0170r1.pdf";>P0170R1
+  https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0170r1.pdf";>P0170R1
   7
__cpp_constexpr >= 201603
 
 
Unary Folds and Empty Parameter Packs
-  http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/p0036r0.pdf";>P0036R0
+  https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/p0036r0.pdf";>P0036R0
   6
__cpp_fold_expressions >= 201603
 
 
Generalizing the Range-Based For Loop
-  http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0184r0.html";>P0184R0
+  https://www.ope

Re: [wwwdocs] gcc-14/changes.htm - Offloading: -lm/-lgfortran is autolinked

[Gerald Pfeifer]

On Fri, 16 Jun 2023, Tobias Burnus wrote:
> Thomas recently improved the offload experience by avoiding to use, e.g.
> 
>   gfortran -O3 -fopenmp qcd.f90 -lblas -foffload-options="-lgfortran -lm"
> 
> as libm and libgfortran now automatically get linked as 'gfortran' links
> -lgfortran and -lm on the host (only those libraries, not others). Thus,
> the commandline now looks much more natural:
> 
>   gfortran -O3 -fopenmp qcd.f90 -lblas

Nice!

> Attached patch documents it in the release notes.
> I loved to hear comments, suggestions, improvements (or even appraisals).

Looks good to me. (Personally I would have written "the math and 
Fortran runtime libraries", which is shorter, but pretty much a matter 
of preference. IOW, keep it as is unless you like it better, too. :-)

One idea might be to show the two invocations - before and after - in the 
release notes as well, at the end of that new entry. Totally up to you, 
too.


For the benefit of the doubt: Okay, thank you!

Gerald

[pushed] wwwdocs: gcc-14: Add list markup for C++ release notes

[Gerald Pfeifer]

List items can only appear in lists. :-)

This fixes up

  commit b38079855ead7f7e358d17bc06642d031de5e29b
  Author: Marek Polacek 
  Date:   Thu Jun 22 14:44:43 2023 -0400

C++26 P2752R3 - Static storage for braced initializers implemented

Gerald

---
 htdocs/gcc-14/changes.html | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 00165740..3f797642 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -76,6 +76,7 @@ a work-in-progress.
 
 C++
 
+
   Several C++26 features have been implemented:
 
   https://wg21.link/P2752R3";>P2752R3, Static storage for
@@ -83,6 +84,7 @@ a work-in-progress.
   
 
   
+
 
 
 
-- 
2.41.0

Re: [pushed] wwwdocs: Add GCC Code of Conduct

[Gerald Pfeifer]

On Tue, 20 Jun 2023, Jason Merrill via Gcc-patches wrote:
> As announced on gcc@.

Here is a minor follow-up that I just pushed.

Gerald


>From f87deaa12cccb4b7398a8ec3b306cb4185aae012 Mon Sep 17 00:00:00 2001
From: Gerald Pfeifer 
Date: Fri, 30 Jun 2023 14:59:27 +0200
Subject: [PATCH] conduct: Fix nested lists

---
 htdocs/conduct.html | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/htdocs/conduct.html b/htdocs/conduct.html
index 8fb62e86..da940a47 100644
--- a/htdocs/conduct.html
+++ b/htdocs/conduct.html
@@ -61,7 +61,7 @@ affect a person's ability to participate within them.
   Be careful in the words that you choose. Be kind to
   others. Do not insult or put down other participants. Harassment and other
   exclusionary behavior aren't acceptable. This includes, but is not limited
-  to:
+  to:
 
   
 Violent threats or language directed against another person.
@@ -73,6 +73,7 @@ affect a person's ability to participate within them.
 Advocating for, or encouraging, any of the above behavior.
 Repeated harassment of others. In general, if someone asks you to 
stop, then stop.
   
+  
 
   When we disagree, try to understand why. Disagreements,
   both social and technical, happen all the time and the GCC community is no
-- 
2.41.0

Re: [PATCH] wwwdocs: gcc-14: mark amdgcn fiji deprecated

[Gerald Pfeifer]

Hi Andrew,

On Fri, 20 Oct 2023, Andrew Stubbs wrote:
>>  Additionally, I wonder whether "Fiji" should be changed to "Fiji
>> (gfx803)" in the first line and whether the  "," should be removed in
>> "The ... configuration ... , and no longer includes".
> Fair enough, how's this version? (I like the comma, even if it is optional.)

it's definitely fine. I do have a recommendation and a question, though 
feel free to go about them as you prefer.

+  The default device architecture is now gfx900 (Vega).

How about starting with this as the first sub-item, as a "positive", 
then follow with the deprecation?

+
+  
+The Fiji (gfx803) device support is now deprecated and will be removed from

Could this be "Fiji (gfx803) device support" without the article?

Gerald

Re: [PATCH htdocs v3] bugs: Mention -D_GLIBCXX_ASSERTIONS and -D_GLIBCXX_DEBUG

[Gerald Pfeifer]

On Thu, 26 Oct 2023, Sam James wrote:
> These options both enabled more checking within the C++ standard library 
> and can expose errors in submitted code.

This is a good addition, thank you! I was going to approve/push, but it's 
probably better for Jonathan to give the final okay.

Just one question:

> +... If either of these fail, this is a strong indicator
> +of an error in your code.

What does "fails" mean in this context? Are we looking at build failures?
Run-time failures?

Gerald

Re: [committed] libstdc++: Minor update to installation docs

[Gerald Pfeifer]

On Mon, 18 Sep 2023, Jonathan Wakely via Gcc-patches wrote:
> @@ -103,8 +103,10 @@ ln -s libiconv-1.16 libiconv
>   
> If GCC 3.1.0 or later on is being used on GNU/Linux, an attempt
> will be made to use "C" library functionality necessary for
> -   C++ named locale support.  For GCC 4.6.0 and later, this
> -   means that glibc 2.3 or later is required.
> +   C++ named locale support, e.g. the newlocale
> +   and uselocale functions.
> +   For GCC 4.6.0 and later,
> +   this means that glibc 2.3 or later is required.

Do we still need to provide those details on GCC 3.1+ and GCC 4.6+?

Would it make sense to simply require glibc 2.3 (or higher)?

Gerald

[pushed] libstdc++: Adjust "The Component Object Model" reference

[Gerald Pfeifer]

Pushed.

Gerald


libstdc++-v3/ChangeLog:

* doc/xml/manual/policy_data_structures_biblio.xml: Adjust
"The Component Object Model" reference.
* doc/html/manual/policy_data_structures.html: Regenerate.
---
 libstdc++-v3/doc/html/manual/policy_data_structures.html  | 4 ++--
 libstdc++-v3/doc/xml/manual/policy_data_structures_biblio.xml | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/libstdc++-v3/doc/html/manual/policy_data_structures.html 
b/libstdc++-v3/doc/html/manual/policy_data_structures.html
index cbe9ea21c7c..927b4125587 100644
--- a/libstdc++-v3/doc/html/manual/policy_data_structures.html
+++ b/libstdc++-v3/doc/html/manual/policy_data_structures.html
@@ -1157,7 +1157,7 @@
. 
  Cambridge University Press
. [biblio.mscom] 
-   https://docs.microsoft.com/en-us/windows/win32/com/the-component-object-model";
 target="_top">
+   https://learn.microsoft.com/en-us/windows/win32/com/the-component-object-model";
 target="_top">
  The Component Object Model

   . 
@@ -1297,4 +1297,4 @@
Wickland
  . 
  National Psychological Institute
-   . Prev??Up??NextImplementation??Home??Using
\ No newline at end of file
+   . Prev??Up??NextImplementation??Home??Using
diff --git a/libstdc++-v3/doc/xml/manual/policy_data_structures_biblio.xml 
b/libstdc++-v3/doc/xml/manual/policy_data_structures_biblio.xml
index 1adba7df91d..1450b8fc000 100644
--- a/libstdc++-v3/doc/xml/manual/policy_data_structures_biblio.xml
+++ b/libstdc++-v3/doc/xml/manual/policy_data_structures_biblio.xml
@@ -1061,7 +1061,7 @@
 
   
http://www.w3.org/1999/xlink";
- 
xlink:href="https://docs.microsoft.com/en-us/windows/win32/com/the-component-object-model";>
+ 
xlink:href="https://learn.microsoft.com/en-us/windows/win32/com/the-component-object-model";>
  The Component Object Model

   
-- 
2.39.1

[pushed] libstdc++: Update an open-std.org link

[Gerald Pfeifer]

I *think* I now consistently got www.open-std.org covered throughout the 
entire tree.

Pushed.
Gerald

libstdc++-v3/ChangeLog:

* doc/xml/manual/status_cxx2017.xml: Update an open-std.org link
to www.open-std.org and https.
* doc/html/manual/status.html: Regenerate.
---
 libstdc++-v3/doc/html/manual/status.html   | 2 +-
 libstdc++-v3/doc/xml/manual/status_cxx2017.xml | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/libstdc++-v3/doc/html/manual/status.html 
b/libstdc++-v3/doc/html/manual/status.html
index c99d51ff709..d046bd2de47 100644
--- a/libstdc++-v3/doc/html/manual/status.html
+++ b/libstdc++-v3/doc/html/manual/status.html
@@ -1018,7 +1018,7 @@ since C++14 and the implementation is complete.
 N (components from V1 are still in namespace
 fundamentals_v1)
   Library Fundamentals 2 TS
-   http://open-std.org/JTC1/SC22/WG21/docs/papers/2015/p0013r1.html"; 
target="_top">
+   https://www.open-std.org/JTC1/SC22/WG21/docs/papers/2015/p0013r1.html"; 
target="_top">
  P0013R1

   Logical Operator Type Traits (revision 1)YLibrary Fundamentals 2 TS
diff --git a/libstdc++-v3/doc/xml/manual/status_cxx2017.xml 
b/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
index 7ca63cbad12..bea6db929c6 100644
--- a/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
+++ b/libstdc++-v3/doc/xml/manual/status_cxx2017.xml
@@ -2846,7 +2846,7 @@ since C++14 and the implementation is complete.
 
 
   
-   http://www.w3.org/1999/xlink"; 
xlink:href="http://open-std.org/JTC1/SC22/WG21/docs/papers/2015/p0013r1.html";>
+   http://www.w3.org/1999/xlink"; 
xlink:href="https://www.open-std.org/JTC1/SC22/WG21/docs/papers/2015/p0013r1.html";>
  P0013R1

   
-- 
2.39.1

Re: [committed] wwwdocs: cxx-status: Move www.open-std.org to https

[Gerald Pfeifer]

On Mon, 30 Jan 2023, Gerald Pfeifer wrote:
> On Sun, 31 Jul 2022, Jonathan Wakely wrote:
>> https://www.open-std.org/ says "The site www.open-std.org is holding a
>> number of web pages for groups producing open standards:" but I don't
>> think it really matters which we use.
> It's not a biggie, though consistency never hurts (and makes it harder to 
> miss something). :-)
> 
> At this point we only have two or so instances of open-std.org without
> www. left, and I'll be moving those over as part of some broader changes.

I believe I have changed all open-std.org to www.open-std.org throughout
gcc/ (mostly, though not exclusively libstdc++) and wwwdocs/.

Gerald

[pushed] wwwdocs: news/profiledriven: Update a link

[Gerald Pfeifer]

Pushed.

Gerald
---
 htdocs/news/profiledriven.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/htdocs/news/profiledriven.html b/htdocs/news/profiledriven.html
index 82febc6d..3acacb78 100644
--- a/htdocs/news/profiledriven.html
+++ b/htdocs/news/profiledriven.html
@@ -276,7 +276,7 @@ Frequency and Program Profile Analysis; Wu and Larus; 
MICRO-27.
 
 [4] wwwdocs:
 
-http://www.lighterra.com/papers/valuerangeprop/Patterson1995-ValueRangeProp.pdf";>Accurate
+https://www.lighterra.com/papers/valuerangeprop/Patterson1995-ValueRangeProp.pdf";>Accurate
Static Branch Prediction by Value Range Propagation;
Jason R. C. Patterson (jas...@fit.qut.edu.au), 1995
 
-- 
2.39.1

[pushed] doc: Reword how to get possible values of a parameter (was: Document all param values and remove defaults (PR middle-end/86078))

[Gerald Pfeifer]

On Mon, 24 Sep 2018, Martin Liška wrote:
> As mentioned in the PR we miss defaults for quite some param option.
> I agreed with Richi that easiest way how to fix that would be to remove
> that from documentation and use rather --help=param. It's done in the 
> patch.

And here is a little follow-up patch after that, ahem, little while...

Pushed.

Gerald


gcc/ChangeLog:

* doc/invoke.texi (Optimize Options): Reword the explanation
getting minimal, maximal and default values of a parameter.
---
 gcc/doc/invoke.texi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 6def1fd631e..7b308cd3c31 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -14678,8 +14678,8 @@ The names of specific parameters, and the meaning of 
the values, are
 tied to the internals of the compiler, and are subject to change
 without notice in future releases.
 
-In order to get minimal, maximal and default value of a parameter,
-one can use @option{--help=param -Q} options.
+In order to get the minimal, maximal and default values of a parameter,
+use the @option{--help=param -Q} options.
 
 In each case, the @var{value} is an integer.  The following choices
 of @var{name} are recognized for all targets:
-- 
2.39.1

[wwwdocs] testing: Tweak the link to upstream FTensor (was: Anyone using FTensor to test GCC (or otherwise)?)

[Gerald Pfeifer]

On Tue, 14 Feb 2023, NightStrike wrote:
>> Alas http://www.wlandry.net/Projects/FTensor has been down for a while,
>> and there does not appear to be a new location?
> https://wlandry.net/Projects/FTensor/ works

Ah, indeed. Thank you! Somehow that must have been the one combination I 
did not try.

I pushed the little patch below.

Gerald

commit b74309c36e59105ef0d8e0d91a85a5bfa884e175
Author: Gerald Pfeifer 
Date:   Fri Feb 17 02:19:19 2023 +0100

Tweak the link to upstream FTensor.

diff --git a/htdocs/testing/testing-ftensor.html 
b/htdocs/testing/testing-ftensor.html
index 2e67b4d8..7b1f4675 100644
--- a/htdocs/testing/testing-ftensor.html
+++ b/htdocs/testing/testing-ftensor.html
@@ -11,7 +11,7 @@
 FTensor build and test guide
 
 This page is a guide to running the testing and timing programs for the
-http://www.wlandry.net/Projects/FTensor";>FTensor
+https://wlandry.net/Projects/FTensor";>FTensor
 tensor class library as part of GCC integration testing.
 
 Resource usage

[pushed] doc: Update link to AVR-LibC

[Gerald Pfeifer]

Pushed.

Gerald


gcc/ChangeLog:

* doc/invoke.texi (AVR Options): Update link to AVR-LibC.
---
 gcc/doc/invoke.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index a5ea86f68c9..078d29d5313 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -22888,7 +22888,7 @@ points to.
 The startup code from libgcc never sets @code{EIND}.
 Notice that startup code is a blend of code from libgcc and AVR-LibC.
 For the impact of AVR-LibC on @code{EIND}, see the
-@w{@uref{http://nongnu.org/avr-libc/user-manual/,AVR-LibC user manual}}.
+@w{@uref{https://www.nongnu.org/avr-libc/user-manual/,AVR-LibC user manual}}.
 
 @item
 It is legitimate for user-specific startup code to set up @code{EIND}
-- 
2.39.1

[pushed] wwwdocs: readings: Update link to ETRAX manual

[Gerald Pfeifer]

Pushed.

Gerald
---
 htdocs/readings.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/htdocs/readings.html b/htdocs/readings.html
index d3e443ad..27f42d3d 100644
--- a/htdocs/readings.html
+++ b/htdocs/readings.html
@@ -117,7 +117,7 @@ names.
Manufacturer: Axis Communications
Acronym stands for: Code Reduced Instruction Set
The CRIS architecture is used in the ETRAX system-on-a-chip series.
-   https://www.axis.com/files/tech_notes/etrax_100lx_prog_man-050519.pdf";>Programmer's
 Manual for CRIS v10
+   https://www.axis.com/dam/public/25/67/ab/etrax-100lx-programmer%E2%80%99s-manual-en-US-33419.pdf";>Programmer's
 Manual for CRIS v10
  
  
  C-SKY
-- 
2.39.1

[pushed] libstdc++: Switch two links to www.open-std.org to https

[Gerald Pfeifer]

Famous last words - somehow these escaped my net last week.

Pushed.
Gerald


libstdc++-v3/ChangeLog:

* doc/xml/faq.xml: Switch two links to www.open-std.org to https.
* doc/html/faq.html: Regenerate.
---
 libstdc++-v3/doc/html/faq.html | 4 ++--
 libstdc++-v3/doc/xml/faq.xml   | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/libstdc++-v3/doc/html/faq.html b/libstdc++-v3/doc/html/faq.html
index f49b84c4c33..965aa91d031 100644
--- a/libstdc++-v3/doc/html/faq.html
+++ b/libstdc++-v3/doc/html/faq.html
@@ -541,7 +541,7 @@
 For those people who are not part of the ISO Library Group
 (i.e., nearly all of us needing to read this page in the first
 place), a public list of the library defects is occasionally
-published on http://www.open-std.org/jtc1/sc22/wg21/"; target="_top">the WG21
+published on https://www.open-std.org/jtc1/sc22/wg21/"; target="_top">the WG21
 website.
 Many of these issues have resulted in
 code changes in libstdc++.
@@ -825,7 +825,7 @@
 Yes.
 
 The C++ Standard Library
-http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf"; 
target="_top">
+https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf"; 
target="_top">
 Technical Report 1 added many new features to the library.
 
 The implementation status of TR1 in libstdc++ can be tracked
diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-v3/doc/xml/faq.xml
index 9ae4966ecea..b38091acdc8 100644
--- a/libstdc++-v3/doc/xml/faq.xml
+++ b/libstdc++-v3/doc/xml/faq.xml
@@ -754,7 +754,7 @@
 (i.e., nearly all of us needing to read this page in the first
 place), a public list of the library defects is occasionally
 published on http://www.w3.org/1999/xlink";
-xlink:href="http://www.open-std.org/jtc1/sc22/wg21/";>the WG21
+xlink:href="https://www.open-std.org/jtc1/sc22/wg21/";>the WG21
 website.
 Many of these issues have resulted in
 code changes in 
libstdc++.
@@ -1181,7 +1181,7 @@
 
 
 The C++ Standard Library
-http://www.w3.org/1999/xlink"; 
xlink:href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf";>
+http://www.w3.org/1999/xlink"; 
xlink:href="https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf";>
 Technical Report 1 added many new features to the library.
 
 
-- 
2.39.1

[pushed] wwwdocs: gcc-12: Simplify a sentence in the OpenMP section

[Gerald Pfeifer]

That was a bit too much in terms of additions things. :-)

Pushed.

Gerald
---
 htdocs/gcc-12/changes.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 32403579..fd4062e6 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -153,7 +153,7 @@ You may also want to check out our
   
 OpenMP 5.0 support has been extended: The close map
   modifier and the affinity clause are now supported.
-  In addition Fortran gained additionally the following features which were
+  In addition Fortran gained the following features which were
   available in C and C++ before: declare variant is now
   available, depobj, mutexinoutset and
   iterator can now also be used with the depend
-- 
2.39.1

Re: [pushed] wwwdocs: gcc-12: Simplify a sentence in the OpenMP section

[Gerald Pfeifer]

On Sat, 18 Feb 2023, NightStrike wrote:
> Missing a comma after "in addition" and "features". For the latter, "x that
> y" > no comma. "X, which y" > comma. For the former, it's required to
> separate the prepositional phrase from the subject.

Thanks, and good point. I'll take care of all "In addition"s throughout 
all of wwwdocs.

Gerald

[pushed] wwwdocs: index: Remove link to Nick's blog

[Gerald Pfeifer]

Nick has not been able to update his blog for a while and confirmed
we should remove this link.

Pushed.
 
Gerald (who is missing those nice updates)

---
 htdocs/index.html | 1 -
 1 file changed, 1 deletion(-)

diff --git a/htdocs/index.html b/htdocs/index.html
index 80730c06..3d0f8700 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -89,7 +89,6 @@ mission statement.
 
 
 https://gcc.gnu.org/news.html";>Older news |
-https://developers.redhat.com/author/nick-clifton";>Nick's Blog |
 
 More news? Let ger...@pfeifer.com know!
 
-- 
2.39.1

[pushed] wwwdocs: *: Add a comma after "In addition" when used as transition

[Gerald Pfeifer]

As promised yesterday, this not only improves the one case that
triggered NightStrike's note, but all cases I found in wwwdocs.

Pushed.

Gerald

--

wwwdocs: *: Add a comma after "In addition" when used as transition

On the way reduce one use and simplify a sentence.
---
 htdocs/gcc-12/changes.html | 4 ++--
 htdocs/gcc-3.0/libgcc.html | 2 +-
 htdocs/gcc-5/changes.html  | 2 +-
 htdocs/gcc-6/changes.html  | 2 +-
 htdocs/git.html| 4 ++--
 htdocs/spam.html   | 3 +--
 6 files changed, 8 insertions(+), 9 deletions(-)

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index fd4062e6..c47d3285 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -153,7 +153,7 @@ You may also want to check out our
   
 OpenMP 5.0 support has been extended: The close map
   modifier and the affinity clause are now supported.
-  In addition Fortran gained the following features which were
+  In addition, Fortran gained the following features which were
   available in C and C++ before: declare variant is now
   available, depobj, mutexinoutset and
   iterator can now also be used with the depend
@@ -170,7 +170,7 @@ You may also want to check out our
   align and allocator modifiers to the
   allocate clause and the atomic extensions are
   now available. The OMP_PLACE environment variable supports
-  the OpenMP 5.1 features. In addition the OMP_NUM_TEAMS and
+  the OpenMP 5.1 features. In addition, the OMP_NUM_TEAMS and
   OMP_TEAMS_THREAD_LIMIT environment variables and their
   associated API routines are now supported as well as the 
memory-allocation
   routines added for Fortran and extended for C/C++ in OpenMP 5.1. In
diff --git a/htdocs/gcc-3.0/libgcc.html b/htdocs/gcc-3.0/libgcc.html
index d98f9b71..6143db0c 100644
--- a/htdocs/gcc-3.0/libgcc.html
+++ b/htdocs/gcc-3.0/libgcc.html
@@ -12,7 +12,7 @@
 
 This page provides a summary of discussions about the pros and cons
 of distributing libgcc as a shared library, as well as a
-static library.  In addition this page details the plans regarding
+static library.  In addition, it details the plans regarding
 libgcc for the GCC 3.0 release.
 
 Issues
diff --git a/htdocs/gcc-5/changes.html b/htdocs/gcc-5/changes.html
index 201a039f..6952f866 100644
--- a/htdocs/gcc-5/changes.html
+++ b/htdocs/gcc-5/changes.html
@@ -1001,7 +1001,7 @@ are not listed here).
and built-in support. It is enabled through option 
-mmwaitx.
The instructions monitorx and mwaitx
implement the same functionality as the old monitor
-   and mwait instructions. In addition mwaitx
+   and mwait instructions. In addition, mwaitx
adds a configurable timer. The timer value is received as third
argument and stored in register %ebx.
   
diff --git a/htdocs/gcc-6/changes.html b/htdocs/gcc-6/changes.html
index b400dd9c..0c7d2582 100644
--- a/htdocs/gcc-6/changes.html
+++ b/htdocs/gcc-6/changes.html
@@ -566,7 +566,7 @@ within strings:
and built-in support. It is enabled through option 
-mmwaitx.
The instructions monitorx and mwaitx
implement the same functionality as the old monitor
-   and mwait instructions. In addition mwaitx
+   and mwait instructions. In addition, mwaitx
adds a configurable timer. The timer value is received as third
argument and stored in register %ebx.
  
diff --git a/htdocs/git.html b/htdocs/git.html
index f71b451f..2543c237 100644
--- a/htdocs/git.html
+++ b/htdocs/git.html
@@ -20,8 +20,8 @@
 large.  That way you can pick up any version (including releases) of
 GCC that is in our repository.
 
-In addition you
-can https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git";>browse our
+In addition, you can
+https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git";>browse our
 Git history online.
 
 (Our web pages are managed via Git in a
diff --git a/htdocs/spam.html b/htdocs/spam.html
index 349e70c7..43040100 100644
--- a/htdocs/spam.html
+++ b/htdocs/spam.html
@@ -45,8 +45,7 @@ avoid creating unnecessary traffic:
  harvested.
 
 
-In addition may want to check out
-https://www.abuse.net";>www.abuse.net.
+Also check out https://www.abuse.net";>www.abuse.net.
 
 
 
-- 
2.39.1

[pushed] wwwdocs: gcc-9: Various changes around -flive-patching

[Gerald Pfeifer]

This is on top of what Qing nicely added back in 2018 - backlog on my 
disk.

Pushed.

Gerald
---
 htdocs/gcc-9/changes.html | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/htdocs/gcc-9/changes.html b/htdocs/gcc-9/changes.html
index 7dfae89c..89c20985 100644
--- a/htdocs/gcc-9/changes.html
+++ b/htdocs/gcc-9/changes.html
@@ -101,10 +101,10 @@ You may also want to check out our
   Invoking GCC for more.
   
   
-A new option, https://gcc.gnu.org/onlinedocs/gcc-9.1.0/gcc/Optimize-Options.html#index-flive-patching";>-flive-patching=[inline-only-static|inline-clone]
 wwwdocs:, has been
-introduced to provide a safe compilation for live-patching. At the same
-time, provides multiple-level control on the enabled IPA optimizations.
-See the user guide for more details about the option.
+A new option https://gcc.gnu.org/onlinedocs/gcc-9.1.0/gcc/Optimize-Options.html#index-flive-patching";>-flive-patching=[inline-only-static|inline-clone]
 wwwdocs:
+generates code suitable for live patching. At the same
+time it provides multiple-level control over IPA optimizations.
+See the user guide for more details.
   
   
   A new option, --completion, has been added to provide more 
fine
-- 
2.39.1

Re: [wwwdocs, patch] OpenMP update for gcc-13/changes.html + projects/gomp/

[Gerald Pfeifer]

On Wed, 22 Feb 2023, Tobias Burnus wrote:
> Comments? Suggestions?

OpenMP update for gcc-13/changes.html + projects/gomp/


--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
+  Reverse offload is now supported with nvptx and AMD GCN devices.

Would it make sense to sort AMD GCN and nvptx alphabetically (and in turn 
switch the order)?


>From a wwwdocs perspective the changes look fine.

Thanks,
Gerald

Re: [PATCH 3/7] **/*.texi: Reorder index entries

[Gerald Pfeifer]

Hi Arsen,

On Fri, 27 Jan 2023, Arsen Arsenović via Gcc-patches wrote:
> gcc/d/ChangeLog:
> 
>   * implement-d.texi: Reorder index entries around @items.
> 
> gcc/ChangeLog:
> 
>   * doc/cfg.texi: Reorder index entries around @items.
>   * doc/cpp.texi: Ditto.
>   * doc/cppenv.texi: Ditto.
>   * doc/cppopts.texi: Ditto.
>   * doc/generic.texi: Ditto.
>   * doc/install.texi: Ditto.
>   * doc/invoke.texi: Ditto.
>   * doc/md.texi: Ditto.
>   * doc/rtl.texi: Ditto.
>   * doc/tm.texi: Ditto.
>   * doc/trouble.texi: Ditto.
> 
> gcc/fortran/ChangeLog:
> 
>   * invoke.texi: Reorder index entries around @items.
> 
> gcc/go/ChangeLog:
> 
>   * gccgo.texi: Reorder index entries around @items.

I was going to push this, alas there are now rejects for
fortran/invoke.texi, gcc/doc/invoke.texi and gcc/doc/cppopts.texi.

If you can get me a rebased version I'll give it a try again. (Or
are there some earlier dependencies? I tried to push what I feel
comfortable at this point.)

Gerald

Re: [committed 034/103] gccrs: dump: Emit visibility when dumping items

[Gerald Pfeifer]

Just noticed this by chance: 

How does this patch constitute a functional change (that matches the 
ChangeLog)? It looks it only adds an empty line to the source code?

Gerald

On Tue, 21 Feb 2023, arthur.co...@embecosm.com wrote:
> From: Arthur Cohen 
> 
> gcc/rust/ChangeLog:
> 
>   * ast/rust-ast-dump.cc: Emit visibility when dumping items.
> ---
>  gcc/rust/ast/rust-ast-dump.cc | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/gcc/rust/ast/rust-ast-dump.cc b/gcc/rust/ast/rust-ast-dump.cc
> index fdcd97561bb..b7557bdee0c 100644
> --- a/gcc/rust/ast/rust-ast-dump.cc
> +++ b/gcc/rust/ast/rust-ast-dump.cc
> @@ -835,6 +835,7 @@ void
>  Dump::visit (Function &function)
>  {
>emit_visibility (function.get_visibility ());
> +
>stream << "fn " << function.get_function_name ();
>if (function.has_generics ())
>  emit_generic_params (function.get_generic_params ());

Re: [PATCH+wwwdocs 0/8] A small Texinfo refinement

[Gerald Pfeifer]

On Fri, 27 Jan 2023, Arsen Arsenović via Gcc-patches wrote:
> Some patches from this patchset appear to have been dropped due to size
> limits.  I neglected to compress them last night.  Here they are again:

I pushed 2/8 after spot checking the huge patch.

Just 2 out of 970 hunks FAILED (for gcc/doc/invoke.texi). Do you want to 
re-run your script and see what new may have popped up or is missing?

Thanks,
Gerald

Re: Ping^2: [PATCH+wwwdocs 0/8] A small Texinfo refinement

[Gerald Pfeifer]

On Tue, 21 Feb 2023, Arsen Arsenović wrote:
> Ping.  Like last time, I rebased the series.

Thank you!

> The first two times around, I did not notice there's dedicated
> maintainers for the documentation component, and so, I am adding Gerald,
> Joseph and Sandra to CC this time.  Apologies for the omission.

Much of this is over my head in terms of texinfo, which is why I had 
to defer when I originally saw it. Sorry for not being explicit about
that originally.

That said, I feel sufficiently confident taking care of 2/8 and 3/8 
(see my earlier replies).

I hope Sandra or Joseph will be able to help with others (especially
1, 5, and 6).

Gerald

Re: [PATCH v2 2/5] **/*.texi: Reorder index entries

[Gerald Pfeifer]

On Thu, 23 Feb 2023, Arsen Arsenović wrote:
> This change is a generalization of r13-6292-gddf6fe375d9110.
:
> gcc/d/ChangeLog:
> 
>   * implement-d.texi: Reorder index entries around @items.
> 
> gcc/ChangeLog:
> 
>   * doc/cfg.texi: Reorder index entries around @items.
>   * doc/cpp.texi: Ditto.
>   * doc/cppenv.texi: Ditto.
>   * doc/cppopts.texi: Ditto.
>   * doc/generic.texi: Ditto.
>   * doc/install.texi: Ditto.
>   * doc/extend.texi: Ditto.
>   * doc/invoke.texi: Ditto.
>   * doc/md.texi: Ditto.
>   * doc/rtl.texi: Ditto.
>   * doc/tm.texi.in: Ditto.
>   * doc/trouble.texi: Ditto.
>   * doc/tm.texi: Regenerate.
> 
> gcc/fortran/ChangeLog:
> 
>   * invoke.texi: Reorder index entries around @items.
> 
> gcc/go/ChangeLog:
> 
>   * gccgo.texi: Reorder index entries around @items.

Thank you, Arsen!

I just pushed this.

For now have taken down your original patch set from x/6 to x/4. :-)

Gerald

Re: [wwwdocs] Add revised Texinfo manual CSS

[Gerald Pfeifer]

On Fri, 27 Jan 2023, Arsen Arsenović via Gcc-patches wrote:
>  htdocs/texinfo-manuals.css | 129 +

Thank you - I pushed this.

+/* Texinfo documentation stylesheet.
+   Inspired by the Gnulib manual, 2023-01-26.
+
+   Arsen Arsenović 

Can we rephrase this a bit? Something like "Contributed by" maybe, or 
omitting the name (as we usually do - since I made sure it's in Git)?

Gerald

Re: [wwwdocs, patch] OpenMP update for gcc-13/changes.html + projects/gomp/

[Gerald Pfeifer]

On Thu, 23 Feb 2023, Tobias Burnus wrote:
> PS: I also removed a stray , but admittedly only after the
> commit. I found it by manually running those through the w3 validator
> site. However, I did not see an automatic email, either it takes longer
> or does it no longer run? It did in the past!

You are right, and this is a sore / sad point: validator.w3.org that we
used in the past now only supports interactive sessions. And they even
broke support for the Referer header, so I also had to remove the checking 
link I had embedded in all of our pages.

These days I invoke the validator (via a version of the original script) 
when I see a commit. Which indeed leads to many orders of magnitude longer 
delays.

Sadly I don't have a better alternative. :-(

Gerald

[pushed] wwwdocs: testing: Avoid a duplicate link

[Gerald Pfeifer]

This came up in a conversation with Jan. (We already have a link a bit 
earlier on that page.)

Pushed.

Gerald
---
 htdocs/testing/index.html | 6 ++
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/htdocs/testing/index.html b/htdocs/testing/index.html
index bd6219ab..012ac287 100644
--- a/htdocs/testing/index.html
+++ b/htdocs/testing/index.html
@@ -115,10 +115,8 @@ the testsuite directories.
   Build and test packages that are normally available on your
   platform and for which you have access to source.
   Run benchmarks regularly and report performance regressions.
-  Extend the
-  http://toolchain.lug-owl.de/buildbot/";>build robot to also
-  do local builds, run the testsuite, visualize test result differences
-  and probably use something like
+  Extend the build robot to also do local builds, run the testsuite,
+  visualize test result differences and probably use something like
   http://buildbot.net/";>BuildBot. Some of the
   https://gcc.gnu.org/wiki/CompileFarm";>Compile Farm machines
   could also be used.
-- 
2.39.1

Re: [wwwdocs] gcc-13/porting_to.html: Document C++ -fexcess-precision=standard

[Gerald Pfeifer]

On Thu, 2 Mar 2023, Jakub Jelinek wrote:
> +
> +#include 

Oops, in HTML we need to spell "<" as "<" and ">" as "> - otherwise
the above would be seen as a tag by the name of stdlib.h. ;-)

I pushed the follow-up patch below.

Gerald


commit 935fcdebfb2fb4dcd89edb51ebed5f1be0fb41e5
Author: Gerald Pfeifer 
Date:   Thu Mar 2 23:58:29 2023 +0100

gcc-13: Use < and > where necessary

diff --git a/htdocs/gcc-13/porting_to.html b/htdocs/gcc-13/porting_to.html
index f0ccef69..953e1453 100644
--- a/htdocs/gcc-13/porting_to.html
+++ b/htdocs/gcc-13/porting_to.html
@@ -129,7 +129,7 @@ constants and expressions.  E.g. for 
FLT_EVAL_METHOD equal
 to 2 on ia32:
 
 
-#include 
+#include <stdlib.h>
 void foo (void) { if (1.1f + 3.3f != 1.1L + 3.3L) abort (); }
 void bar (void) { double d = 4.2; if (d == 4.2) abort (); }
 

Re: [wwwdocs] Document allocator_traits::rebind_alloc assertion with GCC 13

[Gerald Pfeifer]

On Thu, 2 Mar 2023, Jonathan Wakely via Gcc-patches wrote:
> Pushed to wwwdocs.

Thank you!

> +If an allocator type Alloc<T>

Note that HTML 5 complains about the use of  and we are using  
instead.

I just pushed the following patch addressing that. (The diff looks a bit 
bigger due to changes re line breaks.)

Gerald


commit 5a75fbda8c3c647b2ef659ffe67a031ee957abe6
Author: Gerald Pfeifer 
Date:   Fri Mar 3 23:41:36 2023 +0100

gcc-13: Use  instead of 

diff --git a/htdocs/gcc-13/porting_to.html b/htdocs/gcc-13/porting_to.html
index 953e1453..733bb254 100644
--- a/htdocs/gcc-13/porting_to.html
+++ b/htdocs/gcc-13/porting_to.html
@@ -150,8 +150,8 @@ previous behavior.
 GCC 13 now checks that allocators used with the standard library
 can be "rebound" to allocate memory for a different type,
 as required by the allocator requirements in the C++ standard.
-If an allocator type Alloc<T>
-cannot be correctly rebound to another type Alloc<U>,
+If an allocator type Alloc<T>
+cannot be correctly rebound to another type Alloc<U>,
 you will get an error like this:
 
 
@@ -161,26 +161,27 @@ you will get an error like this:
 
 
 The assertion checks that rebinding an allocator to its own value type is a
-no-op, which will be true if its rebind member is defined correctly.
+no-op, which will be true if its rebind member is defined 
correctly.
 If rebinding it to its own value type produces a different type,
 then the allocator cannot be used with the standard library.
 
 
 
-The most common cause of this error is an allocator type 
Alloc<T>
-that derives from std::allocator<T> but does not provide its own
-rebind member. When the standard library attempts to rebind the
-allocator using Alloc<T>::rebind<U> it finds the
-std::allocator<T>::rebind<U> member from the base class,
-and the result is std::allocator<U> instead of
-Alloc<U>.
+The most common cause of this error is an allocator type
+Alloc<T> that derives from
+std::allocator<T> but does not provide its own
+rebind member. When the standard library attempts to rebind the
+allocator using Alloc<T>::rebind<U> it finds the
+std::allocator<T>::rebind<U> member from the base
+class, and the result is std::allocator<U> instead of
+Alloc<U>.
 
 
 
-The solution is to provide a correct rebind member as shown below.
-A converting constructor must also be provided, so that that an
-Alloc<U> can be constructed from an Alloc<T>,
-and vice versa:
+The solution is to provide a correct rebind member as shown
+below.  A converting constructor must also be provided, so that that an
+Alloc<U> can be constructed from an
+Alloc<T>, and vice versa:
 
 
 template<class T>
@@ -197,9 +198,10 @@ class Alloc
 
 
 
-Since C++20, there is no rebind member in std::allocator,
-so deriving your own allocator types from std::allocator is simpler
-and doesn't require the derived allocator to provide its own rebind.
+Since C++20, there is no rebind member in
+std::allocator, so deriving your own allocator types from
+std::allocator is simpler and doesn't require the derived
+allocator to provide its own rebind.
 For compatibility with previous C++ standards, the member should still be
 provided. The converting constructor is still required even in C++20.
 

Re: [PATCH] wwwdocs: Document several further C++23 changes

[Gerald Pfeifer]

On Thu, 2 Mar 2023, Jakub Jelinek wrote:
> Tobias mentioned on IRC that assume attribute wasn't mentioned in
> changes.html.  The P1774R8 entry was missing for C++, so I went through
> projects/cxx-status.html#cxx23 and filled in all the missing papers
> which have been implemented newly in GCC 13, plus a small note for C family
> about assume attribute.

Nice!

There was a small markup issue -- unclosed  -- which I fixed 
thusly.

Gerald


commit ec6f12dc7c229ba1662706c14083e6f3a78e2760
Author: Gerald Pfeifer 
Date:   Fri Mar 3 23:53:21 2023 +0100

gcc-13: Properly close an 

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 839b73d0..cb6a9ec2 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -184,7 +184,7 @@ a work-in-progress.
   
   A new statement attribute for C++23 https://wg21.link/p1774r8";>P1774R8 Portable
   assumptions support also in C or older C++:
-https://gcc.gnu.org/onlinedocs/gcc/Statement-Attributes.html#index-assume-statement-attribute";>__attribute__((assume(EXPR)));
+  https://gcc.gnu.org/onlinedocs/gcc/Statement-Attributes.html#index-assume-statement-attribute";>__attribute__((assume(EXPR)));
   
 
 

Re: [PATCH] wwwdocs: Document several further C++23 changes

[Gerald Pfeifer]

On Thu, 2 Mar 2023, Jakub Jelinek wrote:
> +  A new statement attribute for C++23  href="https://wg21.link/p1774r8";>P1774R8 Portable
> +  assumptions support also in C or older C++:

This reads a bit odd to me: is there a comma missing after P1774R8?
And maybe a colon before? Or something like that?

Gerald

Re: [wwwdocs] document modula-2 in gcc-13/changes.html (and index.html)

[Gerald Pfeifer]

Hi Gaius,

apologies, I thought you had pushed the updated patch and only now 
realized it's not in yet.

Please look into the few bits below and then go ahead and push.

On Mon, 6 Feb 2023, Gaius Mulley wrote:
>   * htdocs/frontends.html: An update to say the front end is now in
>   the development trunk.

Here we'd usually simply say

  * frontends: The Modula-2 front end is now on the 
  development trunk.

skiping "An update to say", or at least "An update to" and the "htdocs/" 
port (and adding which front end).

>   * htdocs/gcc-13/changes.html: A description of which dialects are
>   supported and the user level front end changes so far.

  * gcc-13: Note which Modula-2 dialects are...

>   * htdocs/index.html: Proposed news entry.

  * index: Announce Modula-2 inclusion 

(or something like that).

>   * htdocs/onlinedocs/index.html: PDF, PS and HTML documentation
>   links.
  * onlinedocs: Add links to Modula-2 documentation


> +The compiler is operational with GCC 10, GCC 11 GCC 12 (on
   
...GCC 11, and GCC 12...

> +GNU/Linux x86 systems).  The front end is now in the GCC development
> +trunk (GCC 13).  The front end is mostly written in Modula-2 and it
>  includes a bootstrap tool which translates Modula-2 into C/C++.

How about "It is mostly written in Modula-2 and includes..." to avoid
repetition of "the front end"?


Thank you,
Gerald

[pushed] wwwdocs: gcc-13: Spell front end (noun) without dash

[Gerald Pfeifer]

Pushed in alignment with the list in our coding conventions.

Gerald
---
 htdocs/gcc-13/porting_to.html | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/htdocs/gcc-13/porting_to.html b/htdocs/gcc-13/porting_to.html
index 733bb254..170da096 100644
--- a/htdocs/gcc-13/porting_to.html
+++ b/htdocs/gcc-13/porting_to.html
@@ -121,8 +121,9 @@ the operand as an lvalue.
 
 
 Excess precision changes
+
 GCC 13 implements in C++ excess precision 
support
-which has been before implemented just in the C front-end.  The new behavior is
+which has been before implemented just in the C front end.  The new behavior is
 enabled by default in -std=c++NN modes and e.g. when
 FLT_EVAL_METHOD is 1 or 2 affects behavior of floating point
 constants and expressions.  E.g. for FLT_EVAL_METHOD equal
-- 
2.39.1

Re: [wwwdocs] gcc-13/porting_to.html: Document C++ -fexcess-precision=standard

[Gerald Pfeifer]

On Thu, 2 Mar 2023, Jakub Jelinek wrote:
> --- a/htdocs/gcc-13/porting_to.html
> +++ b/htdocs/gcc-13/porting_to.html

> +GCC 13 implements in C++ excess precision 
> support
> +which has been implemented just in the C front-end before.  The new behavior 
> is
> +enabled by default in -std=c++NN modes and when
> +FLT_EVAL_METHOD is 1 or 2 affects behavior of floating point
   ^^
> +constants and expressions.  E.g. for FLT_EVAL_METHOD equal
> +to 2 on ia32:

:

> +will not abort with standard excess precision, because constants and 
> expressions
> +in float or double are evaluated in precision of
> +long double and demoted only on casts or assignments, but will
> +abort with fast excess precision, where whether something is evaluated in
> +precision of long double or not depends on what evaluations are
> +done in the i387 floating point stack or are spilled from it.
> +
> +The -fexcess-precision=fast option can be used to request the
> +previous behavior.

I struggled a bit understanding this and so have come up with what I 
hope is simpler (without changing the meaning).

What do you think of the change below?

Gerald


diff --git a/htdocs/gcc-13/porting_to.html b/htdocs/gcc-13/porting_to.html
index 170da096..8a2822ff 100644
--- a/htdocs/gcc-13/porting_to.html
+++ b/htdocs/gcc-13/porting_to.html
@@ -122,12 +122,14 @@ the operand as an lvalue.
 
 Excess precision changes
 
-GCC 13 implements in C++ excess precision 
support
-which has been before implemented just in the C front end.  The new behavior is
-enabled by default in -std=c++NN modes and e.g. when
-FLT_EVAL_METHOD is 1 or 2 affects behavior of floating point
-constants and expressions.  E.g. for FLT_EVAL_METHOD equal
-to 2 on ia32:
+GCC 13 implements excess precision
+support, which was implemented just in the C front end
+before, in C++. The new behavior is enabled by default in
+-std=c++NN modes and when
+FLT_EVAL_METHOD is 1 or 2 and affects the behavior of
+floating point constants and expressions.
+
+E.g. for FLT_EVAL_METHOD equal to 2 on ia32
 
 
 #include 
@@ -139,11 +141,11 @@ will not abort with standard excess precision, because 
constants and expressions
 in float or double are evaluated in precision of
 long double and demoted only on casts or assignments, but will
 abort with fast excess precision, where whether something is evaluated in
-precision of long double or not depends on what evaluations are
-done in the i387 floating point stack or are spilled from it.
+long double precision depends on what evaluations are
+done in the i387 floating point stack or are spilled from it.
 
-The -fexcess-precision=fast option can be used to request the
-previous behavior.
+The -fexcess-precision=fast option can be used to
+request the previous behavior.
 
 allocator_traits::rebind_alloc 
must be A
 

Re: [PATCH v2 0/5] A small Texinfo refinement

[Gerald Pfeifer]

On Wed, 8 Mar 2023, Sandra Loosemore wrote:
> I personally do not know how the manuals for the GCC web site are built

gcc.gnu.org has texinfo 6.5. (It's a RHEL 8.7 system.)

> If we do update the version, there's a version check in configure.ac and 
> some hack for "makeinfo 4.7 brokenness" in doc/install.texi2html that 
> need to be changed, as well as install.texi.

The note in doc/install.texi2html isn't specific to version 4.7. Rather 
it's about a design decision made then to encode dashes as _002d which
essentially solved a non-issue and isn't practial at all.

Good point - I'll see to update that comment.

Gerald

Re: [PATCH v2 4/5] Update texinfo.tex, remove the @gol macro/alias

[Gerald Pfeifer]

On Thu, 9 Mar 2023, Sandra Loosemore wrote:
> This is OK, but I'd like to see this patch split into two separate 
> commits as well -- one for the texinfo.tex import, and one for the @gol 
> changes.

I believe Arsen does not have git write access.

Arsen, if that is indeed the case, I offer to push these two commits for
you if you send them by e-mail (as two attachments).

Gerald

Re: [PATCH v2 4/5] Update texinfo.tex, remove the @gol macro/alias

[Gerald Pfeifer]

On Fri, 10 Mar 2023, Arsen Arsenović wrote:
> Thanks, Thomas.  I'd be happy to undergo this process later today.  If I
> understood right, I should fill out
> https://sourceware.org/cgi-bin/pdw/ps_form.cgi and name you, right?

Yes. 

(Thomas, you, and me actually could have met a FOSDEM. Next year we should
send a note to the gcc@ list and arrange for something?)

>>> Arsen, if that is indeed the case, I offer to push these two commits for
>>> you if you send them by e-mail (as two attachments).
> Thanks!  Either approach works for me :)

Happy to go the route Thomas suggested (though available to help, too).

Gerald

[pushed] wwwdocs: gcc-13: Escape < and > as < and >

[Gerald Pfeifer]

Note that in HTML < and > have a special meaning, so we cannot simply 
write "<* noreturn *>", but need to escape it as "<* noreturn *>".

Pushed.

Gerald

---
 htdocs/gcc-13/changes.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 17be7e7c..209c13cd 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -383,7 +383,7 @@ a work-in-progress.
 support for the ISO/IEC 10514-1, PIM2, PIM3, PIM4 dialects
 together with a complete set of ISO/IEC 10514-1 and PIM
 libraries.
-  The <* noreturn *> attribute is supported
+  The <* noreturn *> attribute is supported
 with the -Wreturn-type
 https://gcc.gnu.org/onlinedocs/m2/Compiler-options.html";>
   option.
-- 
2.39.2

Re: [PATCH v2 0/5] A small Texinfo refinement

[Gerald Pfeifer]

On Fri, 10 Mar 2023, Sandra Loosemore wrote:
> AFAIK we have not knowingly changed any specific requirements beyond the 
> stated 4.7 and 4.9 for PDF output, but it concerns me that nobody is 
> likely to be using versions that old on a regular basis to make sure 
> they continue to work and we haven't unknowingly introduced dependencies 
> on newer Texinfo features.

I'm generally very interested in ensuring we do not hurt users who do not 
have the latest and greatest of the day. On the other hand, if there's a 
few people using (more or less deliberately abandonware) we should not 
feel too bad if something breaks.

> Anyway, I think I will leave the existing requirement alone for now, and 
> just add a note that newer versions produce better output.

With Richi mentioning that SLE 12 (which was first released 9 years ago) 
uses texinfo 4.13a and Andrew mentioning that RHEL 7 uses texinfo 5.1 I
would feel very comfortable making either 4.13 or even 5.1 the new minimum.

(Not because we need to cater to those two Enterprise Linux distros, 
rather since they tend to fall on the conversative side.)

Gerald

Re: [PATCH v2 1/5] docs: Create Indices appendix

[Gerald Pfeifer]

On Sat, 11 Mar 2023, Arsen Arsenović wrote:
> OK, changed up a bit, what do you think of this:

> maintainer-scripts/ChangeLog:
>
>   * update_web_docs_git: Set CONTENTS_OUTPUT_LOCATION=inline in
>   order to put @shortcontents above contents. See
>   9dd976a4-4e09-d901-b949-6d5037567...@codesourcery.com on
>   gcc-patches.

In the ChangeLog we only describe *what* has change, so the first half of 
the first sentence.

The rest then goes in between the first line of the Git commit message
(= the subject of your mail) and the ChangeLog entries.


> --- a/gcc/configure
> +++ b/gcc/configure

We usually don't post diffs for generated files. Not a biggie, I figured I 
mention it since it makes reviewing easier and patches shorter, and thus 
tends to increase the chance reviewers short on time jump in. :-)


> --- a/maintainer-scripts/update_web_docs_git
> +++ b/maintainer-scripts/update_web_docs_git
> @@ -169,7 +169,7 @@ for file in $MANUALS; do
> if [ "$file" = "gnat_ugn" ]; then
>   includes="$includes -I gcc/gcc/ada -I gcc/gcc/ada/doc/gnat_ugn"
> fi
> -makeinfo --html --css-ref $CSS $includes -o ${file} ${filename}
> +makeinfo --html -c CONTENTS_OUTPUT_LOCATION=inline --css-ref $CSS 
> $includes -o ${file} ${filename}

Sandra deferred to me on this one, so explicitly: Ack, thank you. :-)

Note, update_web_docs_git runs once a day, at 0:50 GMT, see 
gcc/maintainer-scripts/crontab, and needs to be updated on the gcc.gnu.org 
system. I am happy to do that for you, just drop me a note when the commit
is in.

Gerald

Re: [Committed] Docs: Update documentation of Texinfo versions for building manuals.

[Gerald Pfeifer]

On Fri, 10 Mar 2023, Sandra Loosemore wrote:
> I've checked in the attached patch per discussion in another thread about
> possibly updating the minimum required Texinfo version.

Thank you, Sandra!

I was going to udpate the comment in doc/install.texi2html just now, and 
saw you beat me to it (and better than I probably would have done it). :)

> BTW the hardcopy manual being offered for sale in the FSF shop is for 
> GCC 3.3 (2003?), so I felt no compunction about deleting the pointer to 
> it as unhelpful.

Totally, yes.

Gerald

[pushed] wwwdocs: gcc-10: Minor tweaks to the OpenACC/OpenMP section

[Gerald Pfeifer]

I looked at this older release notes "by chance" and notice some minor 
editorial changes.

Pushed (but let me know if you disagree with any of these).

Gerald


---
 htdocs/gcc-10/changes.html | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index 4acc8d12..915e80ae 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -191,8 +191,8 @@ You may also want to check out our
 
 
   
-Version 2.6 of the https://www.openacc.org/";>OpenACC
-specification is now supported in the C, C++ and Fortran compilers.
+Version 2.6 of the https://www.openacc.org";>OpenACC
+specification is now supported by the C, C++ and Fortran compilers.
 See the https://gcc.gnu.org/wiki/OpenACC/Implementation%20Status#status-10";>implementation
 status section on the OpenACC wiki page and the
 https://gcc.gnu.org/onlinedocs/gcc-10.1.0/libgomp/#toc-Enabling-OpenACC-1";>
@@ -200,11 +200,11 @@ You may also want to check out our
   
   GCC 10 adds a number of newly implemented
   https://www.openmp.org/specifications/";>OpenMP 5.0
-  features on top of the GCC 9 release such as conditional
+  features such as conditional
   lastprivate clause, scan and loop
   directives, order(concurrent) and
   use_device_addr clauses support, if
-  clause on simd construct or partial support for
+  clause on simd construct, and partial support for
   the declare variant directive, getting closer to
   full support of the OpenMP 5.0 standard.
   
-- 
2.39.2

[pushed] doc: Drop a redundant link to AVR-LibC

[Gerald Pfeifer]

Pushed.

Gerald


gcc/ChangeLog:

* doc/extend.texi (Named Address Spaces): Drop a redundant link
to AVR-LibC.
---
 gcc/doc/extend.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index e0c5357291b..fd3745c5608 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -7906,7 +7906,7 @@ of the data but not how this data is accessed.
 In order to read data located with the @code{progmem} attribute
 (inline) assembler must be used.
 @smallexample
-/* Use custom macros from 
@w{@uref{http://nongnu.org/avr-libc/user-manual/,AVR-LibC}} */
+/* Use custom macros from AVR-LibC */
 #include  
 
 /* Locate var in flash memory */
-- 
2.39.2

[pushed] wwwdocs: testing: Further adjust link to upstream FTensor

[Gerald Pfeifer]

This aspect I missed in my previous change.

Easy enough to fix. Pushed.

Gerald

---
 htdocs/testing/testing-ftensor.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/htdocs/testing/testing-ftensor.html 
b/htdocs/testing/testing-ftensor.html
index 7b1f4675..1f9de177 100644
--- a/htdocs/testing/testing-ftensor.html
+++ b/htdocs/testing/testing-ftensor.html
@@ -11,7 +11,7 @@
 FTensor build and test guide
 
 This page is a guide to running the testing and timing programs for the
-https://wlandry.net/Projects/FTensor";>FTensor
+https://wlandry.net/Projects/FTensor/";>FTensor
 tensor class library as part of GCC integration testing.
 
 Resource usage
-- 
2.39.2

Re: [PATCH] wwwdocs: Clarify meaning of "not issued by" in bugs web page

[Gerald Pfeifer]

Hi Jonathan,

On Tue, 27 Jul 2021, Jonathan Wakely via Gcc-patches wrote:
> Firstly, these bullet points are full sentences and so should end with
> a period (or smiley, in some cases).
> 
> Secondly, releases are not issued by the GNU Project at all, they're
> issued by the GCC release managers.
> 
> Finally, "releases or snapshots of GCC not issued by ..." has confused
> at least one bug reporter, and I think saying "unofficial releases or
> snapshots" makes it slightly clearer. Comparatively few users actually
> use a self-built GCC based on official source tarballs, but that's OK.
> Distro builds tend to be much closer to upstream these days, and we
> rarely reject bug reports where the reporter is using a build from
> Fedora, Ubuntu, Arch or whatever (unless it really is caused by a
> downstream patch and doesn't reproduce with a gcc.gnu.org release).

I noticed the first part went in back in August 2021, the second did not, 
likely because I failed to ack the patch (and the first part was obviously 
obvious).

Apologies for that. I now pushed the remainder of the original patch as
well; it's just simpler that way.

Gerald


commit 303c5592f31a73cc90e2a799fe0455873db512b2
Author: Jonathan Wakely 
Date:   Sun Mar 12 10:34:21 2023 +0100

bugs: Clarify meaning of "not issued by"

diff --git a/htdocs/bugs/index.html b/htdocs/bugs/index.html
index 765d8c67..3744a28f 100644
--- a/htdocs/bugs/index.html
+++ b/htdocs/bugs/index.html
@@ -116,8 +116,9 @@ three of which can be obtained from the output of gcc 
-v:
   separate projects, with separate mailing lists and different bug
   reporting procedures.
 
-  Bugs in releases or snapshots of GCC not issued by the GNU
-  Project.  Report them to whoever provided you with the release.
+  Bugs in unofficial releases or snapshots of GCC not issued by
+  the GCC project.  Report them to whoever provided you with that
+  version.
 
   Questions about the correctness or the expected behavior of
   certain constructs that are not GCC extensions.  Ask them in forums

[pushed] libstdc++: Move www.graphviz.org to https

[Gerald Pfeifer]

With this there should be only one or two problem links left in all of the 
libstdc++ docs. :-)

Pushed.

Gerald


libstdc++-v3/ChangeLog:

* doc/xml/manual/documentation_hacking.xml: Move www.graphviz.org
to https.
* doc/html/manual/documentation_hacking.html: Regenerate.
---
 libstdc++-v3/doc/html/manual/documentation_hacking.html | 2 +-
 libstdc++-v3/doc/xml/manual/documentation_hacking.xml   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/libstdc++-v3/doc/html/manual/documentation_hacking.html 
b/libstdc++-v3/doc/html/manual/documentation_hacking.html
index 24df9bd9481..047a62e0831 100644
--- a/libstdc++-v3/doc/html/manual/documentation_hacking.html
+++ b/libstdc++-v3/doc/html/manual/documentation_hacking.html
@@ -122,7 +122,7 @@
   
To generate the pretty pictures and hierarchy
graphs, the
-   http://www.graphviz.org"; 
target="_top">Graphviz package
+   https://www.graphviz.org"; 
target="_top">Graphviz package
will need to be installed. For PDF
output, https://tug.org/applications/pdftex/"; 
target="_top">
pdflatex is required as well as a number of TeX packages
diff --git a/libstdc++-v3/doc/xml/manual/documentation_hacking.xml 
b/libstdc++-v3/doc/xml/manual/documentation_hacking.xml
index 20f96ed7205..692b724ca11 100644
--- a/libstdc++-v3/doc/xml/manual/documentation_hacking.xml
+++ b/libstdc++-v3/doc/xml/manual/documentation_hacking.xml
@@ -271,7 +271,7 @@
   
To generate the pretty pictures and hierarchy
graphs, the
-   http://www.w3.org/1999/xlink"; 
xlink:href="http://www.graphviz.org";>Graphviz package
+   http://www.w3.org/1999/xlink"; 
xlink:href="https://www.graphviz.org";>Graphviz package
will need to be installed. For PDF
output, http://www.w3.org/1999/xlink"; 
xlink:href="https://tug.org/applications/pdftex/";>
pdflatex is required as well as a number of TeX packages
-- 
2.39.2

Re: [PATCH v2 1/5] docs: Create Indices appendix

[Gerald Pfeifer]

On Sat, 11 Mar 2023, Arsen Arsenović wrote:
> Sandra Loosemore  writes:
>> Hmmm, first off, I think somebody other than me needs to approve the 
>> configure and makefile pieces, as well as the maintainer-scripts part. 
>> It looks conceptually right to me

Per gcc/MAINTAINERS that'd be

  build machinery (*.in)  Paolo Bonzini   
  build machinery (*.in)  Nathanael Nerode
  build machinery (*.in)  Alexandre Oliva 
  build machinery (*.in)  Ralf Wildenhues 

though I don't recall seeing much (if anything) from others than Alexandre 
for quite a while.

So more likely one of the Global Reviewers in that same file.

Gerald

[pushed] wwwdocs: style: Add a link to our testing page

[Gerald Pfeifer]

Jan suggested we add this link, restoring in a way, though now pointing to 
our general testing page.

Pushed.

(Note: gcc.gnu.org will take a couple of hours to pick up this change.)

Gerald

---
 htdocs/style.mhtml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/htdocs/style.mhtml b/htdocs/style.mhtml
index 1b778151..dcc27cc4 100644
--- a/htdocs/style.mhtml
+++ b/htdocs/style.mhtml
@@ -121,6 +121,7 @@
   Front ends
   Back ends
   Extensions
+  Testing
   Benchmarks
   Translations
   
-- 
2.39.2

Re: [wwwdocs] document modula-2 in gcc-13/changes.html (and index.html)

[Gerald Pfeifer]

The patch is now in, alas all the GNU M2 manual links now point to 
non-existant locations.

Does maintainer-scripts/update_web_docs_git require an update to cover 
Modula-2 and actually build the manual we are now linking to (or rather
trying to)?

Gerald

[pushed] maintainer-scripts: Abstract BUGURL in update_web_docs_git

[Gerald Pfeifer]

The URL where to report bugs is hard coded in two places; abstract that
into one variable, defined up front.

maintainer-scripts/ChangeLog:

* update_web_docs_git (BUGURL): Introduce and use throughout.
---
 maintainer-scripts/update_web_docs_git | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/maintainer-scripts/update_web_docs_git 
b/maintainer-scripts/update_web_docs_git
index dee9b1d3b5e..1c6a993cafd 100755
--- a/maintainer-scripts/update_web_docs_git
+++ b/maintainer-scripts/update_web_docs_git
@@ -33,6 +33,7 @@ MANUALS="cpp
   libiberty
   porting"
 
+BUGURL="http://gcc.gnu.org/bugs/";
 CSS=/gcc.css
 
 WWWBASE=${WWWBASE:-"/www/gcc/htdocs"}
@@ -154,11 +155,11 @@ includedir=gcc/gcc/doc/include
fi
echo "@set srcdir $WORKDIR/gcc/gcc"
echo "@set VERSION_PACKAGE (GCC)"
-   echo "@set BUGURL @uref{http://gcc.gnu.org/bugs/}";
+   echo "@set BUGURL @uref{$BUGURL}"
 ) > $includedir/gcc-vers.texi
 
 # Generate libquadmath-vers.texi.
-echo "@set BUGURL @uref{http://gcc.gnu.org/bugs/}"; \
+echo "@set BUGURL @uref{$BUGURL}" \
   > $includedir/libquadmath-vers.texi
 
 # Now convert the relevant files from texi to HTML, PDF and PostScript.
-- 
2.39.2

Re: [PATCH] wwwdocs: Clarify experimental status of C++17 prior to GCC 9

[Gerald Pfeifer]

On Wed, 22 Mar 2023, Jonathan Wakely via Gcc-patches wrote:
> We don't currently have a single page where you can find out when
> support for a given standard became non-experimental (you have to look
> through all the gcc-X/changes.html pages to find it). I think we should
> have that info on the cxx-status.html page. This adds it for C++17, and
> we can do the same for C++20 when we declare that stable.

I'm not sure why I only noticed this today. Just a little technicality
to fix this page. 

Pushed.

Gerald


Commit a09e584729 introduced an  without corresponding .
---
 htdocs/projects/cxx-status.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html
index 7f59e5a2..675fbcd0 100644
--- a/htdocs/projects/cxx-status.html
+++ b/htdocs/projects/cxx-status.html
@@ -402,7 +402,7 @@
 -->
   
 
-  C++20 Support in GCC
+  C++20 Support in GCC
 
   GCC has experimental support for the latest revision of the C++
   standard, which was published in 2020.
-- 
2.40.1

[pushed] wwwdocs: gcc-13/buildstat: Remove trace of XHTML

[Gerald Pfeifer]

Hi Jakub,

do you recall how this snuck in? None of other other pages has had
  <..." />
instead of
  <...">
for a while. Not a biggie at all, just curious.

Pushed.


On a related note, the buildstat pages for GCC 9, 10, 11, 12, and 13
all are empty and I suggest to remove them. Any concerns?

Gerald

---
 htdocs/gcc-13/buildstat.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/htdocs/gcc-13/buildstat.html b/htdocs/gcc-13/buildstat.html
index fd6ee9e7..a54d0214 100644
--- a/htdocs/gcc-13/buildstat.html
+++ b/htdocs/gcc-13/buildstat.html
@@ -4,7 +4,7 @@
 
 
 Build status for GCC 13
-https://gcc.gnu.org/gcc.css"; />
+https://gcc.gnu.org/gcc.css";>
 
 
 
-- 
2.40.1

[pushed] wwwdocs: onlinedocs/13.1.0: Remove last trace of XHTML

[Gerald Pfeifer]

This is how I actually noticed the situation in gcc-13/buildstat.html
(and then I mixed the two up).

Jakub, do you have some old templates somewhere maybe?

Gerald

Pushed:
---
 htdocs/onlinedocs/13.1.0/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/htdocs/onlinedocs/13.1.0/index.html 
b/htdocs/onlinedocs/13.1.0/index.html
index 7b8c3d38..2abc06ac 100644
--- a/htdocs/onlinedocs/13.1.0/index.html
+++ b/htdocs/onlinedocs/13.1.0/index.html
@@ -4,7 +4,7 @@
 
 
 GCC 13.1 manuals
-https://gcc.gnu.org/gcc.css"; />
+https://gcc.gnu.org/gcc.css";>
 
 
 
-- 
2.40.1

[pushed] libstdc++: Move lafstern.org reference to https

[Gerald Pfeifer]

Pushed.

Gerald


libstdc++-v3/ChangeLog:

* doc/xml/manual/strings.xml: Move lafstern.org reference to https.
* doc/html/manual/strings.html: Regenerate.
---
 libstdc++-v3/doc/html/manual/strings.html | 2 +-
 libstdc++-v3/doc/xml/manual/strings.xml   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/libstdc++-v3/doc/html/manual/strings.html 
b/libstdc++-v3/doc/html/manual/strings.html
index 3441119e926..ceb09f97eac 100644
--- a/libstdc++-v3/doc/html/manual/strings.html
+++ b/libstdc++-v3/doc/html/manual/strings.html
@@ -111,7 +111,7 @@
book Exceptional C++ and on his 
website as http://www.gotw.ca/gotw/029.htm"; 
target="_top">GotW 29.
See?  Told you it was easy!
  Added June 2000: The May 2000 
issue of C++
- Report contains a fascinating http://lafstern.org/matt/col2_new.pdf"; target="_top"> article by
+ Report contains a fascinating https://lafstern.org/matt/col2_new.pdf"; target="_top"> article by
  Matt Austern (yes, the Matt 
Austern) on why
  case-insensitive comparisons are not as easy as they seem, and
  why creating a class is the wrong 
way to go
diff --git a/libstdc++-v3/doc/xml/manual/strings.xml 
b/libstdc++-v3/doc/xml/manual/strings.xml
index e9d4c8ce347..b0dab645a2d 100644
--- a/libstdc++-v3/doc/xml/manual/strings.xml
+++ b/libstdc++-v3/doc/xml/manual/strings.xml
@@ -145,7 +145,7 @@
See?  Told you it was easy!

  Added June 2000: The May 2000 issue of C++
- Report contains a fascinating http://www.w3.org/1999/xlink"; 
xlink:href="http://lafstern.org/matt/col2_new.pdf";> article by
+ Report contains a fascinating http://www.w3.org/1999/xlink"; 
xlink:href="https://lafstern.org/matt/col2_new.pdf";> article by
  Matt Austern (yes, the Matt Austern) on why
  case-insensitive comparisons are not as easy as they seem, and
  why creating a class is the wrong way to go
-- 
2.40.1

[pushed] wwwdocs: preprocess: Check whether input files exist

[Gerald Pfeifer]

This has not come up in all those years since the preprocess script
usually is invoked from other scripts, notably post commit hooks. It
can, however, be invoked manually, and error handling is generally a
good thing.

Instead of
   cat: foo/bar/index.html: No such file or directory
   New file /www/gcc/htdocs/foo/bar/index.html
and an empty output file, we now get
   Input file foo/bar/index.html not found.
when invoking `preprocess foo/bar/index.html`.

Pushed.
Gerald
---
 bin/preprocess | 5 +
 1 file changed, 5 insertions(+)

diff --git a/bin/preprocess b/bin/preprocess
index c62ba457..c6d34c4b 100755
--- a/bin/preprocess
+++ b/bin/preprocess
@@ -155,6 +155,11 @@ process_file()
 # Strip possibly leading "./".
 f=`echo $1 | sed -e 's#^\./##'`
 
+if [ ! -f "$SOURCETREE/$f" ] wwwdocs:; then
+echo "Input file $f not found."
+return
+fi
+
 if [ ! -d "$DESTTREE/`dirname $f`" ] wwwdocs:; then
 echo "Creating new directory `dirname $f`."
 mkdir -p $DESTTREE/`dirname $f`
-- 
2.40.1

[pushed 1/N] install.texi: Remove alpha*-*-* section

[Gerald Pfeifer]

install.texi has become a bit blown up over the years, with good potential 
to trim chaff and simplify things for our users.

This is just one step of possibly many more.

Pushed.

Gerald


gcc/ChangeLog:

* doc/install.texi (Specific): Remove de facto empty alpha*-*-*
section.
---
 gcc/doc/install.texi | 11 ---
 1 file changed, 11 deletions(-)

diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index fa91ce1953d..fadcf5aa2ef 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -3633,8 +3633,6 @@ information have to.
 @item
 @uref{#aarch64-x-x,,aarch64*-*-*}
 @item
-@uref{#alpha-x-x,,alpha*-*-*}
-@item
 @uref{#amdgcn-x-amdhsa,,amdgcn-*-amdhsa}
 @item
 @uref{#amd64-x-solaris2,,amd64-*-solaris2*}
@@ -3836,15 +3834,6 @@ types of branch protections.  Conversely,
 protections by default.  This mechanism is turned off by default if neither
 of the options are given at configure time.
 
-@html
-
-@end html
-@anchor{alpha-x-x}
-@heading alpha*-*-*
-This section contains general configuration information for all
-Alpha-based platforms using ELF@.  In addition to reading this
-section, please read all other sections that match your target.
-
 @html
 
 @end html
-- 
2.40.1

[pushed] wwwdocs: readings: Adjust link to Arm architectures

[Gerald Pfeifer]

arm.com does some interesting special effects with URL; hopefully this 
simplification is somewhat resilient.

Pushed.

Gerald
---
 htdocs/readings.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/htdocs/readings.html b/htdocs/readings.html
index 6813b84f..26f2af7a 100644
--- a/htdocs/readings.html
+++ b/htdocs/readings.html
@@ -65,7 +65,7 @@ names.
   The 64-bit execution state of the ARM Architecture, first introduced
   by the ARMv8-A architecture.
   Manufacturer: Various, by license from ARM.
-  https://developer.arm.com/architectures/cpu-architecture";>ARM 
Documentation
+  https://developer.arm.com/architectures";>ARM Documentation
  
 
  andes (nds32)
@@ -84,7 +84,7 @@ names.
  ARM
   Manufacturer: Various, by license from ARM.
   CPUs include: ARM7TDMI, and the Cortex-A, Cortex-R and Cortex-M series.
-  https://developer.arm.com/architectures/cpu-architecture";>ARM 
Documentation
+  https://developer.arm.com/architectures";>ARM Documentation
   https://developer.arm.com/documentation/ihi0036/latest/";>Application 
Binary Interface (ABI) for the ARM Architecture
  
 
-- 
2.40.1

Re: [PATCH] Deprecate the BRIG/HSAIL front-end (Was: Re: [committed] doc: Remove HSAIL from Language Standards)

[Gerald Pfeifer]

On Tue, 26 Jan 2021, Martin Jambor wrote:
> I have discussed this with Pekka and we concluded that deprecating the
> HSAIL/BRIG front-end is the right thing to do.  Therefore, I'd like to
> propose the following patch to the documentation repo.  Is it OK?

> +  The front-end for compiling BRIG format of Heterogeneous System
> +  Architecture Intermediate Language (HSAIL) has been deprecated
> +  and will likely be removed in a future release.

Please use "front end" for the noun, per codingconventions.html .

This looks fine with that little change.

Thanks,
Gerald

Re: [commited] [PR99378] LRA: Skip decomposing address for asm insn operand with unknown constraint

[Gerald Pfeifer]

On Fri, 5 Mar 2021, Vladimir Makarov via Gcc-patches wrote:
>   The following patch fixes
> 
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99378
> 
>   The patch was successfully bootstrapped and tested on x86-64.

Is it possible this breaks bootstrap on i586?

See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99438

  .../libgcc/soft-fp/divtf3.c: In function '__divtf3':
  .../libgcc/soft-fp/divtf3.c:51:1: error: unrecognizable insn:
   51 | }
  | ^
(insn 1185 3357 3676 80 (parallel [
(set (reg:SI 5 di [621])
(asm_operands:SI ("sub{l} {%11,%3|%3,%11}
sbb{l} {%9,%2|%2,%9}
sbb{l} {%7,%1|%1,%7}
sbb{l} {%5,%0|%0,%5}") ("=r") 0 [
(reg:SI 5 di [621])
(mem/c:SI (plus:SI (reg/f:SI 6 bp)
(const_int -80 [0xffb0])) [5 
A_f[2]+0 S4 A64])
(reg:SI 1 dx [622])
(mem/c:SI (plus:SI (reg/f:SI 6 bp)
(const_int -84 [0xffac])) [5 
A_f[1]+0 S4 A32])
(reg:SI 0 ax [623])
(mem/c:SI (plus:SI (reg/f:SI 6 bp)

Gerald

Re: [wwwdocs] gcc-12/changes.html (GCN): >1 workers per gang

[Gerald Pfeifer]

On Mon, 9 Aug 2021, Tobias Burnus wrote:
> Comments and/or suggestions?

Looks good from my perspective, with the feedback that Thomas
provided.

(Is "CU" a sufficiently established term, or might it make sense
to spell it out?)

Thanks,
Gerald

Re: [committed] Drop stabs support from h8300 and v850 ports

[Gerald Pfeifer]

On Thu, 19 Aug 2021, Jeff Law via Gcc-patches wrote:
> Whee, two more ports dropping stabs. Committed to the trunk.

Are you saying you're on a mission to stab wodden stakes into stabs?

SCNR :-)
Gerald

[committed] wwwdocs: Replace reference to gccupc.org with the new site on Github.

[Gerald Pfeifer]

Also shorten some text, call GCC that instead of GNU GCC compiler,
and remove some bits and links where there appears no equivalent
available on that new site.

Pushed.

Gerald
---
 htdocs/frontends.html |  2 +-
 htdocs/git.html   |  2 +-
 htdocs/projects/gupc.html | 33 +++--
 3 files changed, 9 insertions(+), 28 deletions(-)

diff --git a/htdocs/frontends.html b/htdocs/frontends.html
index 2d996cbd..bec33b7b 100644
--- a/htdocs/frontends.html
+++ b/htdocs/frontends.html
@@ -64,7 +64,7 @@ Currently they only support GNU/Linux x86 systems.
 http://pl1gcc.sourceforge.net/";>PL/1 for GCC is a
 GCC front end for the PL/I language.
 
-http://www.gccupc.org/";>GCC Unified Parallel C
+https://github.com/Intrepid/GUPC";>GCC Unified Parallel C
 (GCC UPC) is a compilation and execution environment for Unified
 Parallel C.
 
diff --git a/htdocs/git.html b/htdocs/git.html
index 905ce80e..96a921df 100644
--- a/htdocs/git.html
+++ b/htdocs/git.html
@@ -478,7 +478,7 @@ in Git.
   high-performance, parallel systems with access to a single
   potentially large, global shared address space.
   Further information can be found on the
-  http://gccupc.org";>GNU UPC web page.
+  https://github.com/Intrepid/GUPC";>GNU UPC page.
 
   pph
   This branch implements https://gcc.gnu.org/wiki/pph";> Pre-Parsed
diff --git a/htdocs/projects/gupc.html b/htdocs/projects/gupc.html
index 3b822ca3..0c55c571 100644
--- a/htdocs/projects/gupc.html
+++ b/htdocs/projects/gupc.html
@@ -16,11 +16,10 @@
 
 The GNU UPC project implements a compilation and execution environment for
 programs written in the
-https://www.gccupc.org";>UPC (Unified Parallel C) language.
-The GNU UPC compiler extends the capabilities of the
-GNU GCC compiler. The GUPC compiler is
-implemented as a C Language dialect translator, in a fashion similar to the
-implementation of the GNU Objective C compiler.
+https://github.com/Intrepid/GUPC";>UPC (Unified Parallel C)
+language.  The GNU UPC compiler extends the capabilities of GCC.
+The GUPC compiler is implemented as a C Language dialect translator, in
+a fashion similar to the implementation of the GNU Objective C compiler.
 
 
 Project Goal
@@ -79,29 +78,11 @@ on a platform of interest to you, we recommend that you 
join the
 
 Download
 
-The latest release of GUPC can be downloaded from https://www.gccupc.org/download";>gccupc.org.
-
-
-Alternatively, read-only SVN access to the GUPC branch can be used to
-acquire the latest development source tree:
-
-
-svn checkout svn://gcc.gnu.org/svn/gcc/branches/gupc
+The https://github.com/Intrepid/GUPC/releases";>latest
+release of GUPC is available for download.
 
-Documentation
+Alternatively, you can access the GUPC branch in the GCC sources.
 
-For a list of configuration switches that you can use to build GUPC, consult
-the GUPC
-http://gccupc.org/gnu-upc-info/gnu-upc-install-from-source-code";>
-configuration page.
-
-
-For a quick summary of the switches used to compile and link a UPC program,
-consult the GUPC
-http://gccupc.org/gnu-upc-info/gnu-upc-compile-options";>
-manual page.
-
 
 The GNU UPC Discussion List
 
-- 
2.28.0

Re: [wwwdocs][patch] gcc-13/changes.html: Add nvptx's --with-arch

[Gerald Pfeifer]

Hi Tobias,

On Wed, 28 Sep 2022, Tobias Burnus wrote:
> The attached patch documents the new nvptx configure flag 
> --with-arch=sm_...
> 
> Comments? OK?

where it reads

+  https://gcc.gnu.org/install/specific.html#nvptx-x-none";>
+  --with-arch= flag; if not specified, GCC defaults to
+  sm_30. GCC's target libraries are build both with
+  sm_30 and the specified target architecture.

I suggest "configure option" instead of "flag" (if that's it, of course). 
 
And I'd start the following as a full sentence "If not specified", or in 
fact omit it, since "GCC defaults" already implies "If not specified"?

"are build" -> "are then built", and switch the last two sentences?

Okay with those changes (or telling me I'm wrong ;-).

Gerald

[committed] wwwdocs: gcc5: Remove broken link to Intel ISA extensions

[Gerald Pfeifer]

I doubt anyone is using the GCC 5 release notes to get to that page,
and the link broke without a proper redirect, so make it a textual
reference (only).

Pushed.

Gerald

---
 htdocs/gcc-5/changes.html | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/htdocs/gcc-5/changes.html b/htdocs/gcc-5/changes.html
index 2e2e20e6..6f5b9f64 100644
--- a/htdocs/gcc-5/changes.html
+++ b/htdocs/gcc-5/changes.html
@@ -779,8 +779,7 @@ here.
 
 IA-32/x86-64
   
-New https://software.intel.com/sites/default/files/managed/39/c5/325462-sdm-vol-1-2abcd-3abcd.pdf";>ISA
 extensions
+New ISA extensions
support AVX-512{BW,DQ,VL,IFMA,VBMI} of Intel's CPU
codenamed Skylake Server was added to GCC.  That includes inline
assembly support, new intrinsics, and basic autovectorization.  These
-- 
2.35.1

[committed] wwwdocs: sched-treegion.html: Move prod.tinker.cc.gatech.edu to https

[Gerald Pfeifer]

Just following server redirects - http to https.

Pushed.

Gerald
---
 htdocs/projects/sched-treegion.html | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/htdocs/projects/sched-treegion.html 
b/htdocs/projects/sched-treegion.html
index d421d87b..d5cefa03 100644
--- a/htdocs/projects/sched-treegion.html
+++ b/htdocs/projects/sched-treegion.html
@@ -162,7 +162,7 @@ rules apply.  This branch is maintained by
 Readings
 
 Lots of useful information is present at the http://prod.tinker.cc.gatech.edu";>TINKER Microarchitecture and
+href="https://prod.tinker.cc.gatech.edu";>TINKER Microarchitecture and
 Compiler Research homepage. More relevant papers:
 
 
@@ -170,7 +170,7 @@ Compiler Research homepage. More relevant papers:
 
 
 H. Zhou, and T.M. Conte, 
-http://prod.tinker.cc.gatech.edu/symposia/interact02.pdf";>
+https://prod.tinker.cc.gatech.edu/symposia/interact02.pdf";>
 Code Size Efficiency in Global Scheduling for ILP Processors,
 Proceedings of the 6th Annual Workshop on the Interaction between Compilers 
 and Computer Architectures (INTERACT-6), Cambridge, MA, February 2002.
@@ -180,7 +180,7 @@ and Computer Architectures (INTERACT-6), Cambridge, MA, 
February 2002.
 
 
 H. Zhou, M. D. Jennings, and T. M. Conte,
-http://prod.tinker.cc.gatech.edu/symposia/lcpc01.pdf";>
+https://prod.tinker.cc.gatech.edu/symposia/lcpc01.pdf";>
 Tree Traversal Scheduling: A Global Scheduling Technique for VLIW/EPIC 
 Processors, Proceedings of the 14th Annual Workshop on Languages and 
 Compilers for Parallel Computing (LCPC'01), Cumberland Falls, KY, August 2001.
@@ -190,7 +190,7 @@ Compilers for Parallel Computing (LCPC'01), Cumberland 
Falls, KY, August 2001.
 
 
 W. A. Havanki, S. Banerjia, and T. M. Conte,
-http://prod.tinker.cc.gatech.edu/symposia/hpca4_treegions.pdf";>
+https://prod.tinker.cc.gatech.edu/symposia/hpca4_treegions.pdf";>
 Treegion scheduling for wide-issue processors, Proceedings of the 
 4th International Symposium on High-Performance Computer Architecture 
 (HPCA-4), Las Vegas, Feb. 1998.
@@ -200,7 +200,7 @@ Treegion scheduling for wide-issue processors, 
Proceedings of the
 
 
 S. Banerjia, W.A. Havanki, and T.M. Conte,
-http://prod.tinker.cc.gatech.edu/symposia/europar97.pdf";>
+https://prod.tinker.cc.gatech.edu/symposia/europar97.pdf";>
 Treegion scheduling for highly parallel processors, 
 Proceedings of the 3rd International Euro-Par Conference (Euro-Par'97), 
 Passau, Germany, pp.1074-1078, Aug. 1997.
-- 
2.35.1

[PATCH] wwwdocs: fedora-devel-list archives changes

[Gerald Pfeifer]

I have *NOT* pushed this yet, looking for feedback:

It appears redhat.com has lost Fedora mailing list archives, which are
now at lists.fedoraproject.org using completely different tooling.

Jakub, is there a better way than the patch below?

Gerald

diff --git a/htdocs/gcc-4.3/porting_to.html b/htdocs/gcc-4.3/porting_to.html
index 630290ce..5301729f 100644
--- a/htdocs/gcc-4.3/porting_to.html
+++ b/htdocs/gcc-4.3/porting_to.html
@@ -527,7 +527,7 @@ svn diff -r529854:529855 
http://svn.apache.org/repos/asf/ant/core/trunk/src/main
 
 
 Jakub Jelinek,
-https://listman.redhat.com/archives/fedora-devel-list/2008-January/msg00128.html";>
+https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/WV3KUDEP2JNOWGWES42RQZFYFNLFLAMJ/";>
 Mass rebuild status with gcc-4.3.0-0.4 of rawhide-20071220
 
 

[committed] wwwdocs: gcc-11: Switch from to using ids.

[Gerald Pfeifer]

I - or rather the w3 validator :) - realized that the use of 
is deprecated, so use id attributes instead.

Gerald
---
 htdocs/gcc-11/changes.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 8e6d4ec8..c9eb2295 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -1097,7 +1097,7 @@ is built as FAT libraries containing both 32 bit and 64 
bit objects.
 
 
 
-GCC 11.1
+GCC 11.1
 
 This is the https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=11.0";>list
 of problem reports (PRs) from GCC's bug tracking system that are
@@ -1106,7 +1106,7 @@ complete (that is, it is possible that some PRs that have 
been fixed
 are not listed here).
 
 
-GCC 11.2
+GCC 11.2
 
 This is the https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=11.2";>list
 of problem reports (PRs) from GCC's bug tracking system that are
@@ -1116,7 +1116,7 @@ are not listed here).
 
 
 
-GCC 11.3
+GCC 11.3
 
 Target Specific Changes
 
-- 
2.35.1

Re: [PATCH] wwwdocs: fedora-devel-list archives changes

[Gerald Pfeifer]

On Tue, 15 Mar 2022, Jonathan Wakely wrote:
>> It appears redhat.com has lost Fedora mailing list archives, which are
>> now at lists.fedoraproject.org using completely different tooling.
>>
>>Jakub, is there a better way than the patch below?
> This looks right to me, I don't think there's a better way to link to
> those archives.

Thank you, Jonathan.  I now pushed my patch.

Gerald

[committed] wwwdocs: contribute: Move validator.w3.org to https

[Gerald Pfeifer]

Pushed.

Gerald
---
 htdocs/contribute.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/htdocs/contribute.html b/htdocs/contribute.html
index c0223738..c985b87d 100644
--- a/htdocs/contribute.html
+++ b/htdocs/contribute.html
@@ -145,7 +145,7 @@ eliminate them all.
 Web Site Changes
 
 Changes to the web site must
-http://validator.w3.org/";>validate as HTML 5.  To
+https://validator.w3.org";>validate as HTML 5.  To
 validate your changes, use the "upload file" mode of the
 validator.
 
-- 
2.35.1

[committed] wwwdocs: readings: www.cmass.com is gone, remove

[Gerald Pfeifer]

I pushed this for now.

Gaius, if you want to make changes to that section of readings.html,
absolutely be free doing so (and I'll be happy help, too).

Gerald

---
 htdocs/readings.html | 1 -
 1 file changed, 1 deletion(-)

diff --git a/htdocs/readings.html b/htdocs/readings.html
index 12755d7e..8689eab8 100644
--- a/htdocs/readings.html
+++ b/htdocs/readings.html
@@ -569,7 +569,6 @@ names.
 Modula 3 information
 
 
-  http://www.cmass.com";>http://www.cmass.com
   http://www.modula3.org";>http://www.modula3.org
 
 
-- 
2.35.1

Re: [wwwdocs] Add Ada's changelog entry

[Gerald Pfeifer]

On Mon, 4 Apr 2022, Fernando Oleo Blanco via Gcc-patches wrote:
> this is my first patch to GCC, if there is anything off, please, say
> so. I have used the default HTML formatting that comes with Emacs.

I am not familiar with that Emacs mode, but < and > are special characters 
in HTML and have to be written as < (less than) and > (greater than) 
respectively.

On Mon, 11 Apr 2022, Arnaud Charlet via Gcc-patches wrote:
> Thank you, I've just merged your contribution.

This is the first batch of fixes. Pushed.

Gerald


commit 67c72bb30309882ce465519e97fb14592d18ff2c
Author: Gerald Pfeifer 
Date:   Wed Apr 13 22:43:05 2022 -0600

gcc-12: Properly escape < and >.

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index bd9e5122..057d1274 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -205,10 +205,10 @@ a work-in-progress.
   
 Fixed lower bound for unconstrained arrays.
 
-  type Matrix is array (Natural range 0 .. <>, Natural
-range 0 .. <>) of Integer; is now valid.
+  type Matrix is array (Natural range 0 .. <>,
+   Natural range 0 .. <>) of Integer; is now valid.
   Subtypes can also specify a lower bound: subtype
-String_1 is String (1 .. <>);. Boundaries from slices
+String_1 is String (1 .. <>);. Boundaries from slices
 will "slide" to the correct lower bound of the subtype.