Re: [PATCH wwwdocs] gcc-14: Add code examples for -Wreturn-mismatch

[Sam James]

Florian Weimer  writes:

> ---
>  htdocs/gcc-14/porting_to.html | 46 
> ---
>  1 file changed, 43 insertions(+), 3 deletions(-)
>
> diff --git a/htdocs/gcc-14/porting_to.html b/htdocs/gcc-14/porting_to.html
> index bbbaa25a..123b5e9f 100644
> --- a/htdocs/gcc-14/porting_to.html
> +++ b/htdocs/gcc-14/porting_to.html
> @@ -213,19 +213,59 @@ in functions which are declared to return 
> void, or
>  return statements without expressions for functions
>  returning a non-void type.
>  
> +
> +Both function definitions below contain -Wreturn-mismatch
> +errors:
> +
> +
> +void
> +do_something (int flag)
> +{
> +  if (!flag)
> +return -1;
> +  do_something_else ();
> +}
> +
> +int
> +unimplemented_function (void)
> +{
> +  puts ("unimplemented function foo called");
> +}
> +
> +
> +
>  
>  To address this, remove the incorrect expression (or turn it into a
>  statement expression immediately prior to the return
>  statements if the expression has side effects), or add a dummy return
> -value, as appropriate.  If there is no suitable dummy return value,
> -further changes may be needed to implement appropriate error handling.
> +value, as appropriate.
> +
> +
> +void
> +do_something (int flag)
> +{
> +  if (!flag)
> +return -1;
> +  do_something_else ();
> +}
> +
> +int
> +unimplemented_function (void)
> +{
> +  puts ("unimplemented function foo called");
> +  return 0;
> +}
> +
> +
> +If there is no suitable dummy return value, further changes may be
> +needed to implement appropriate error handling.

LGTM.

>  
>  
>  Previously, these mismatches were diagnosed as
>  a -Wreturn-type warning.  This warning still exists, and
>  is not treated as an error by default.  It now covers remaining
>  potential correctness issues, such as reaching the closing
> -brace } of function that does not
> +brace } of a function that does not
>  return void.
>  
>  
>
> base-commit: 5ef0adf3098478600f0c108e07e568d864b4c731



signature.asc
Description: PGP signature

Re: [PATCH wwwdocs] gcc-14: Some very common historic Autoconf probes that no longer work

[Sam James]

Florian Weimer  writes:

> ---
>  htdocs/gcc-14/porting_to.html | 43 
> +++
>  1 file changed, 43 insertions(+)
>
> diff --git a/htdocs/gcc-14/porting_to.html b/htdocs/gcc-14/porting_to.html
> index 123b5e9f..ab65c5e7 100644
> --- a/htdocs/gcc-14/porting_to.html
> +++ b/htdocs/gcc-14/porting_to.html
> @@ -437,6 +437,49 @@ issues addressed in more recent versions.)  Versions 
> before 2.69 may
>  have generic probes (for example for standard C support) that rely on
>  C features that were removed in C99 and thus fail with GCC 14.
>  
> +
> +Older Autoconf versions (for example, Autoconf 2.13) generate core
> +probes that are incompatible with C99.  These include the basic
> +compiler functionality check:
> +
> +
> +#include "confdefs.h"
> +main(){return(0);}
> +
> +
> +And a check for standard C compatibility:
> +
> +
> +#define XOR(e, f) (((e) && !(f)) || (!(e) && (f)))
> +int main () { int i; for (i = 0; i  256; i++)
> +if (XOR (islower (i), ISLOWER (i)) || toupper (i) != TOUPPER (i)) exit(2);
> +exit (0); }
> +
> +

Consider adding the check name so it shows up on search engine results?

("Checking for $X ... no")

> +(Several variants with different line breaks and whitespace were in
> +use.)  If it is not possible to port the configure script to current
> +Autoconf, these issues can be patched directly:
> +
> +
> +#include "confdefs.h"
> +int main(){return(0);}
> +
> +
> +And for the second probe:
> +
> +
> +#define XOR(e, f) (((e) && !(f)) || (!(e) && (f)))
> +int main () { int i; for (i = 0; i  256; i++)
> +if (XOR (islower (i), ISLOWER (i)) || toupper (i) != TOUPPER (i)) 
> return 2;
> +return 0; }
> +
> +
> +There is a long tail of less frequent issues, involving keyword
> +checking (for inline), and checks for dlopen
> +and mmap.  A setvbuf probe was previously
> +expected to fail at run time because it triggered undefined behavior,
> +now it fails because of a compilation error.
> +
>  Turning errors back into warnings
>  
>  

LGTM otherwise.

>
> base-commit: 1fcd61437d6a3d7bf24b993b09d525486dc9a2e5



signature.asc
Description: PGP signature

Re: [PATCH wwwdocs] CSS: Color markup for /

[Gerald Pfeifer]

On Sat, 17 Feb 2024, Florian Weimer wrote:
> In addition to underlines and strikethroughs.  This makes it easier to 
> spot the differences in example code changes.

Looks like a good idea!

Thanks,
Gerald

[PATCH wwwdocs] gcc-14: Some very common historic Autoconf probes that no longer work

[Florian Weimer]

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

diff --git a/htdocs/gcc-14/porting_to.html b/htdocs/gcc-14/porting_to.html
index 123b5e9f..ab65c5e7 100644
--- a/htdocs/gcc-14/porting_to.html
+++ b/htdocs/gcc-14/porting_to.html
@@ -437,6 +437,49 @@ issues addressed in more recent versions.)  Versions 
before 2.69 may
 have generic probes (for example for standard C support) that rely on
 C features that were removed in C99 and thus fail with GCC 14.
 
+
+Older Autoconf versions (for example, Autoconf 2.13) generate core
+probes that are incompatible with C99.  These include the basic
+compiler functionality check:
+
+
+#include "confdefs.h"
+main(){return(0);}
+
+
+And a check for standard C compatibility:
+
+
+#define XOR(e, f) (((e) && !(f)) || (!(e) && (f)))
+int main () { int i; for (i = 0; i  256; i++)
+if (XOR (islower (i), ISLOWER (i)) || toupper (i) != TOUPPER (i)) exit(2);
+exit (0); }
+
+
+(Several variants with different line breaks and whitespace were in
+use.)  If it is not possible to port the configure script to current
+Autoconf, these issues can be patched directly:
+
+
+#include "confdefs.h"
+int main(){return(0);}
+
+
+And for the second probe:
+
+
+#define XOR(e, f) (((e) && !(f)) || (!(e) && (f)))
+int main () { int i; for (i = 0; i  256; i++)
+if (XOR (islower (i), ISLOWER (i)) || toupper (i) != TOUPPER (i)) return 
2;
+return 0; }
+
+
+There is a long tail of less frequent issues, involving keyword
+checking (for inline), and checks for dlopen
+and mmap.  A setvbuf probe was previously
+expected to fail at run time because it triggered undefined behavior,
+now it fails because of a compilation error.
+
 Turning errors back into warnings
 
 

base-commit: 1fcd61437d6a3d7bf24b993b09d525486dc9a2e5

[PATCH wwwdocs] gcc-14: Add code examples for -Wreturn-mismatch

[Florian Weimer]

---
 htdocs/gcc-14/porting_to.html | 46 ---
 1 file changed, 43 insertions(+), 3 deletions(-)

diff --git a/htdocs/gcc-14/porting_to.html b/htdocs/gcc-14/porting_to.html
index bbbaa25a..123b5e9f 100644
--- a/htdocs/gcc-14/porting_to.html
+++ b/htdocs/gcc-14/porting_to.html
@@ -213,19 +213,59 @@ in functions which are declared to return 
void, or
 return statements without expressions for functions
 returning a non-void type.
 
+
+Both function definitions below contain -Wreturn-mismatch
+errors:
+
+
+void
+do_something (int flag)
+{
+  if (!flag)
+return -1;
+  do_something_else ();
+}
+
+int
+unimplemented_function (void)
+{
+  puts ("unimplemented function foo called");
+}
+
+
+
 
 To address this, remove the incorrect expression (or turn it into a
 statement expression immediately prior to the return
 statements if the expression has side effects), or add a dummy return
-value, as appropriate.  If there is no suitable dummy return value,
-further changes may be needed to implement appropriate error handling.
+value, as appropriate.
+
+
+void
+do_something (int flag)
+{
+  if (!flag)
+return -1;
+  do_something_else ();
+}
+
+int
+unimplemented_function (void)
+{
+  puts ("unimplemented function foo called");
+  return 0;
+}
+
+
+If there is no suitable dummy return value, further changes may be
+needed to implement appropriate error handling.
 
 
 Previously, these mismatches were diagnosed as
 a -Wreturn-type warning.  This warning still exists, and
 is not treated as an error by default.  It now covers remaining
 potential correctness issues, such as reaching the closing
-brace } of function that does not
+brace } of a function that does not
 return void.
 
 

base-commit: 5ef0adf3098478600f0c108e07e568d864b4c731

[PATCH wwwdocs] CSS: Color markup for /

[Florian Weimer]

In addition to underlines and strikethroughs.  This makes it easier to
spot the differences in example code changes.

---
 htdocs/gcc.css | 4 
 1 file changed, 4 insertions(+)

diff --git a/htdocs/gcc.css b/htdocs/gcc.css
index 77d01ee0..e32c4b93 100644
--- a/htdocs/gcc.css
+++ b/htdocs/gcc.css
@@ -98,6 +98,10 @@ div.copyright p:nth-child(3) { margin-bottom: 0; }
 .blue{ color:blue; }
 .blackbg { color:white; background-color: #00; }
 
+/* Inline markup for differences. */
+ins { background-color: lightgreen }
+del { background-color: pink } 
+
 /* Quote an e-mail.  The first  has the sender, the second the quote. */
 blockquote.mail div:nth-child(2) { border-left: solid blue; padding-left: 4pt; 
}
 

base-commit: 848ebfb46379178be3b0307c2ef99f4012e40edd

Re: [pushed] wwwdocs: gcc-14: Fix typo in AVR section

[Georg-Johann Lay]

Am 14.02.24 um 01:40 schrieb Gerald Pfeifer:

Note that  is not part of current HTML standards; can we simply
remove it?


Hi Gerald,

thanks for looking into this.

The  is not strictly needed, I just has the case that
"-Wl,--defsym,__RODATA_FLASH_START__=32k" had a line-break in it.

In addition, I believe it might be good to rephrase that sentence. Do you 
mean "the linker will not pull in that code from ... any more"?


Yes.  When the symbol is satisfied by --defsym, then the code is not
dragged or pulled from that static lib.  I am not a native speaker,
and it is great when you fix any awkward formulations or grammar.

Thanks a lot

Johann


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

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 6ac7c8b1..92bd0a7b 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -370,7 +370,7 @@ a work-in-progress.
precedence over __flmap.
For example, linking with
-Wl,--defsym,__RODATA_FLASH_START__=32k
-   choses the second 32KiB block.
+   chooses the second 32KiB block.
The default uses the last 32KiB block, which is also the
hardware default for bit-field NVMCTRL_CTRLB.FLMAP.
When a non-default block is used,

[pushed] wwwdocs: index: Update link to FOSDEM announcement

[Gerald Pfeifer]

Pushed.

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

diff --git a/htdocs/index.html b/htdocs/index.html
index ed505637..032cc4b6 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -55,7 +55,7 @@ mission statement.
 News
 
 
-https://inbox.sourceware.org/36fadb0549c3dca716eb3b923d66a11be2c67a61.ca...@redhat.com;>GCC
 developer room at FOSDEM 2024: Call for Participation open
+https://inbox.sourceware.org/gcc/36fadb0549c3dca716eb3b923d66a11be2c67a61.ca...@redhat.com;>GCC
 developer room at FOSDEM 2024: Call for Participation open
 [2023-11-20] wwwdocs:
 FOSDEM 2024: Brussels, Belgium, February 3-4 2024
 
-- 
2.43.0

[pushed] wwwdocs: gcc-14: Fix typo in AVR section

[Gerald Pfeifer]

Note that  is not part of current HTML standards; can we simply 
remove it?

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

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 6ac7c8b1..92bd0a7b 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -370,7 +370,7 @@ a work-in-progress.
precedence over __flmap.
For example, linking with
-Wl,--defsym,__RODATA_FLASH_START__=32k
-   choses the second 32KiB block.
+   chooses the second 32KiB block.
   The default uses the last 32KiB block, which is also the
hardware default for bit-field NVMCTRL_CTRLB.FLMAP.
   When a non-default block is used,
-- 
2.43.0

[pushed] wwwdocs: gcc-14: Fix markup in avr section.

[Gerald Pfeifer]

In addition, I believe it might be good to rephrase that sentence. Do you 
mean "the linker will not pull in that code from ... any more"?

Gerald

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

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index cd5f5157..6ac7c8b1 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -390,7 +390,7 @@ a work-in-progress.
can be used:
 __asm (".global __flmap_lock"  "\n\t"
"__flmap_lock = 1");
-  When you do not want the code from#931, then define global
+  When you do not want the code from#931, then define global
symbol __do_flmap_init and the linker will no more drag
that code from libmcu.a.
   In order to return to the old placement of read-only data in RAM,
-- 
2.43.0

Re: [committed][gcc-wwwdocs] Add blurb about bitfield signedness on mcore

[Jeff Law]

On 2/7/24 14:23, Gerald Pfeifer wrote:

On Tue, 19 Dec 2023, Jeff Law wrote:

Pushed to the trunk.


Is this minor follow-up okay, adding a full stop and shortening a bit?

Yes, of course.

Thanks.
jeff

Re: [committed][gcc-wwwdocs] Add blurb about bitfield signedness on mcore

[Gerald Pfeifer]

On Tue, 19 Dec 2023, Jeff Law wrote:
> Pushed to the trunk.

Is this minor follow-up okay, adding a full stop and shortening a bit?

Gerald

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 6d917535..dbc77493 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -504,7 +504,7 @@ a work-in-progress.
 
 
   Bitfields are now signed by default per GCC policy.  If you need 
bitfields
-to be unsigned, then use -funsigned-bitfields
+to be unsigned, use -funsigned-bitfields.
   
 
 

Re: [wwwdocs] Add 2 more C++26 core papers

[Marek Polacek]

On Wed, Feb 07, 2024 at 10:58:18AM +0100, Jakub Jelinek wrote:
> Hi!
> 
> cppreference has 2 more Kona papers listed and it seems eel.is/c++draft/
> has those papers incorporated.
> 
> Ok for wwwdocs?

Patch is OK.  W3 validates fine too.  Thanks,
 
> diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html
> index c265edc0..65030980 100644
> --- a/htdocs/projects/cxx-status.html
> +++ b/htdocs/projects/cxx-status.html
> @@ -117,12 +117,24 @@
> __cpp_placeholder_variables >= 202306L 
>  
>  
> +
> +   Pack indexing 
> +   https://wg21.link/P2662R3;>P2662R3
> +href="https://gcc.gnu.org/PR113798;>No
> +   __cpp_pack_indexing >= 202311L 
> +
>  
> Removing deprecated arithmetic conversion on enumerations 
>https://wg21.link/P2864R2;>P2864R2 ( href="./cxx-dr-status.html">DR) 
> 14
> 
>  
> +
> +   Template parameter initialization 
> +   https://wg21.link/P2308R1;>P2308R1 ( href="./cxx-dr-status.html">DR) 
> +href="https://gcc.gnu.org/PR113800;>No
> +   
> +
>  

[wwwdocs] Add 2 more C++26 core papers

[Jakub Jelinek]

Hi!

cppreference has 2 more Kona papers listed and it seems eel.is/c++draft/
has those papers incorporated.

Ok for wwwdocs?

diff --git a/htdocs/projects/cxx-status.html b/htdocs/projects/cxx-status.html
index c265edc0..65030980 100644
--- a/htdocs/projects/cxx-status.html
+++ b/htdocs/projects/cxx-status.html
@@ -117,12 +117,24 @@
__cpp_placeholder_variables >= 202306L 
 
 
+
+   Pack indexing 
+   https://wg21.link/P2662R3;>P2662R3
+   https://gcc.gnu.org/PR113798;>No
+   __cpp_pack_indexing >= 202311L 
+
 
Removing deprecated arithmetic conversion on enumerations 
   https://wg21.link/P2864R2;>P2864R2 (DR) 
14

 
+
+   Template parameter initialization 
+   https://wg21.link/P2308R1;>P2308R1 (DR) 
+   https://gcc.gnu.org/PR113800;>No
+   
+
 

Re: [wwwdocs] tweak for sourceware account request alias

[Gerald Pfeifer]

On Thu, 11 Jan 2024, Frank Ch. Eigler wrote:
> diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html
:
> -overse...@gcc.gnu.org to add access to the GCC repository.
> +admin-reque...@sourceware.org to add access to the GCC 
> repository.

Thanks, Frank. I just pushed this. 

(Sorry, I had thought this was a FYI note and missed that it wasn't live.)

Gerald

Re: [wwwdocs][patch] gcc-14/changes.html (amdgcn): Update for gfx1030/gfx1100

[Andrew Stubbs]

On 26/01/2024 17:06, Tobias Burnus wrote:

Mention that gfx1030/gfx1100 are now supported.

As noted in another thread, LLVM 15's assembler is now required, before 
LLVM 13.0.1 would do. (Alternatively, disabling gfx1100 support would 
do.) Hence, the added link to the install documentation.


Comments, suggestions?


I'm happy with the technical correctness of this, but I'm uncertain if 
"which required an update of the default build requirements" is the sort 
of wording we like in the changelog?


Perhaps like this?

  Initial support for the AMD Radeon gfx1030 (RDNA2) and
  gfx1100 (RDNA3) devices has been added.  LLVM 15+
  (assembler and linker) is required to support gfx1100.

Andrew

[wwwdocs][patch] gcc-14/changes.html (amdgcn): Update for gfx1030/gfx1100

[Tobias Burnus]

Mention that gfx1030/gfx1100 are now supported.

As noted in another thread, LLVM 15's assembler is now required, before 
LLVM 13.0.1 would do. (Alternatively, disabling gfx1100 support would 
do.) Hence, the added link to the install documentation.


Comments, suggestions?

Tobias
gcc-14/changes.html (amdgcn): Update for gfx1030/gfx1100

Signed-off-by: Tobias Burnus 

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index a04b62ff..2d777f52 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -329,6 +329,11 @@ a work-in-progress.
 AMD Radeon (GCN)
 
 
+  Initial support for the AMD Radeon gfx1030 (RDNA2) and
+gfx1100 (RDNA3) devices has been added, which required an
+update of the default
+https://gcc.gnu.org/install/specific.html#amdgcn-x-amdhsa;>build
+requirements for the build.
   Improved register usage and performance on CDNA Instinct MI100
 and MI200 series devices.
   The default device architecture is now gfx900 (Vega).

[wwwdocs] Document new additions to libstdc++

[Jonathan Wakely]

Pushed to wwwdocs.

-- >8 --

std::generator, std::format improvements, std::text_encoding.
---
 htdocs/gcc-14/changes.html | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 5644de1e..951d005b 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -245,6 +245,7 @@ a work-in-progress.
   Improved experimental support for C++20, including:
 
 std::chrono::parse.
+Unicode-aware string handling in std::format.
 
   
   Improved experimental support for C++23, including:
@@ -252,6 +253,9 @@ a work-in-progress.
 The std::ranges::to function for converting
   ranges to containers.
 
+The std::generator view for getting results from
+  coroutines.
+
 The stacktrace header is supported by default.
 
 std::print and std::println
@@ -272,7 +276,13 @@ a work-in-progress.
 Functions for saturation arithmetic on integers.
 std::to_string now uses std::format.
 Enhanced formatting of pointers with std::format.
+The std::runtime_format function to allow using
+  non-literal format strings with std::format.
 Testable result types for charconv functions.
+The std::text_encoding class for identifying character
+  sets (requires linking with -lstdc++exp for some member
+  functions).
+
 
   
   Faster numeric conversions using std::to_string and
-- 
2.43.0

Re: [wwwdocs][PATCH] gcc-14/changes: Update APX inline asm behavior for x86_64

[Hongyu Wang]

I'm going to check-in this if no objection

Hongyu Wang  于2024年1月9日周二 15:14写道：
>
> Hi,
>
> This patch adds missing description for inline asm behavior and related
> compiler switch for APX.
>
> Ok for gcc-wwwdocs?
>
> ---
>  htdocs/gcc-14/changes.html | 6 ++
>  1 file changed, 6 insertions(+)
>
> diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
> index e3a68998..73a90d30 100644
> --- a/htdocs/gcc-14/changes.html
> +++ b/htdocs/gcc-14/changes.html
> @@ -342,6 +342,12 @@ a work-in-progress.
>NDD, PPX and PUSH2POP2. APX support is available via the
>-mapxf compiler switch.
>
> +  For inline asm support with APX, by default the EGPR feature was
> +  disabled to prevent potential illegal instruction with EGPR occurs.
> +  To invoke egpr usage in inline asm, use new compiler option
> +  -mapx-inline-asm-use-gpr32 and user should ensure the instruction
> +  supports EGPR.
> +  
>New ISA extension support for Intel AVX10.1 was added.
>AVX10.1 intrinsics are available via the -mavx10.1 or
>-mavx10.1-256 compiler switch with 256-bit vector size
> --
> 2.31.1
>

[patch,wwwdocs,avr,applied] Add AVR news for v14.

[Georg-Johann Lay]

https://gcc.gnu.org/gcc-14/changes.html#avr

Johann

--

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 9c9dfa44..8c738683 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -342,7 +342,55 @@ a work-in-progress.
   
 

-
+AVR
+
+  On AVR64* and AVR128* devices, read-only data is now located in 
program

+memory per default and no more in RAM.
+
+  Only a 32KiB block of program memory can be used to store
+   .rodata in that way. Which block is used can be selected by
+   defining symbol __flmap.
+   As an alternative, the byte address of the block can be specified
+   by symbol __RODATA_FLASH_START__ which takes
+   precedence over __flmap.
+  The default uses the last 32KiB block, which is also the
+   hardware default for bit field NVMCTRL_CTRLB.FLMAP.
+  When a block other than the last 32 KiB block is used  to store
+   .rodata, then NVMCTRL_CTRLB.FLMAP
+   must be initialized accordingly by hand, or a version of
+   AVR-LibC that implementshttps://github.com/avrdudes/avr-libc/issues/931;>#931
+   must be used. The latter initializes NVMCTRL_CTRLB.FLMAP
+   in the startup code and according to the value
+   of__flmap resp.
+   __RODATA_FLASH_START__.
+  When AVR-LibC with#931 is used, then defining symbol
+   __flmap_lock to a non-zero value will set bit
+   NVMCTRL_CTRLB.FLMAPLOCK. This will protect
+   NVMCTRL_CTRLB.FLMAP from any further changes 
+   which would be Undefined Behaviour in C/C++.
+  In order to return to the old placement of read-only data in RAM,
+   the new compiler option -mrodata-in-ram can be used.
+  Read-only data is located in output section .rodata,
+   wheras it is part of .text when located in RAM.
+  The feature is only available when the compiler is configured
+   with a version of Binutils that implements
+   https://sourceware.org/PR31124;>PR31124, which is the
+   case for Binutilsv2.42 and up.
+
+  
+  A new compiler option -m[no]-rodata-in-ram has been 
added.
+The default is to locate read-only data in program memory for 
devices that

+support it, e.g. for AVR64* and AVR128* devices as explained above,
+and for devices from the
+href="https://gcc.gnu.org/onlinedocs/gcc/AVR-Options.html#avrxmega3;>avrxmega3

+and
+href="https://gcc.gnu.org/onlinedocs/gcc/AVR-Options.html#avrtiny;>avrtiny 
families.

+  
+  The new built-in macro __AVR_RODATA_IN_RAM__ is 
supported

+on all devices. Its defined to  0 or 1.
+  
+

 IA-32/x86-64
 

[wwwdocs] Document additional symbols in libstdc++exp.a for GCC 13.3

[Jonathan Wakely]

The first two paragraphs are cloned from existing text for other point
releases. The third paragraph documents a recent backport that should be
called out in the release notes.

Pushed to wwwdocs.

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

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index b4b1a39a..6930bd58 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -858,6 +858,32 @@ known to be fixed in the 13.2 release. This list might not 
be
 complete (that is, it is possible that some PRs that have been fixed
 are not listed here).
 
+
+GCC 13.3
+
+Note: GCC 13.3 has not been released yet, so this section is a
+work-in-progress.
+
+This is the https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVEDresolution=FIXEDtarget_milestone=13.3;>list
+of problem reports (PRs) from GCC's bug tracking system that are
+known to be fixed in the 13.3 release. This list might not be
+complete (that is, it is possible that some PRs that have been fixed
+are not listed here).
+
+Language Specific Changes
+
+C++
+
+  
+The libstdc++exp.a library now includes all the Filesystem TS
+symbols from the libstdc++fs.a library,
+and the experimental symbols for the C++23 std::stacktrace
+class from the libstdc++_libbacktrace.a library.
+This means that -lstdc++exp is the only library needed for
+all experimental libstdc++ features.
+  
+
+
 
 
 
-- 
2.43.0

[wwwdocs] Update notes on libstdc++ header dependency changes in GCC 14

[Jonathan Wakely]

Some failures related to std::find_if and stdint types were observed
doing mass rebuilds with GCC 14.

Pushed to wwwdocs.

---
 htdocs/gcc-14/porting_to.html | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/htdocs/gcc-14/porting_to.html b/htdocs/gcc-14/porting_to.html
index dea9ac80..3e4cedc3 100644
--- a/htdocs/gcc-14/porting_to.html
+++ b/htdocs/gcc-14/porting_to.html
@@ -38,10 +38,14 @@ be included explicitly when compiling with GCC 14:
 
 
  algorithm
-  (for std::copy_n, std::lower_bound,
+  (for std::copy_n, std::find_if,
+  std::lower_bound,
   std::remove, std::reverse,
   std::sort etc.)
 
+ cstdint
+  (for std::int8_t, std::int32_t etc.)
+
 
 
 
-- 
2.43.0

[wwwdocs] tweak for sourceware account request alias

[Frank Ch. Eigler]

diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html
index 0c146aba44d2..c89cdb8fb2ef 100644
--- a/htdocs/gitwrite.html
+++ b/htdocs/gitwrite.html
@@ -36,7 +36,7 @@ be sponsored by an existing maintainer (someone with "write 
after approval"
 is not sufficient).
 
 If you already have an account on sourceware.org / gcc.gnu.org, ask
-overse...@gcc.gnu.org to add access to the GCC repository.
+admin-reque...@sourceware.org to add access to the GCC repository.
 Include the name of your sponsor and CC: them.
 Otherwise use https://sourceware.org/cgi-bin/pdw/ps_form.cgi;>this form,

Re: [wwwdocs] gcc-14/changes.html: OpenMP - improve wording

[Tobias Burnus]

Ups - now attached. Thanks Martin!

Martin Jambor wrote:

On Mon, Jan 08 2024, Tobias Burnus wrote:

The attached patch


there was no patch attached to your message.

Martin


does a tiny updated to the OpenMP features (AMD GCN
now also has an optimized memcpy_rect not only nvptx), but the main
change is some shifting around to make it more consistent and better
readable.

I intend to commit this relatively soon; like always, comments and
suggestions are welcome - be it before or after the commit.

Current version: http://gcc.gnu.org/gcc-14/changes.html

Thanks,

Tobiasgcc-14/changes.html: OpenMP - improve wording

This is mostly some shifting of items in bullet points to make it
more organized; it also improved the wording a bit. And there is one
new feature: the optimization for omp_target_memcpy_rect is now also
done for AMD GPUs and not only for nvptx.

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index e3a68998..2c64cf67 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -49,14 +49,24 @@ a work-in-progress.
 
   https://gcc.gnu.org/projects/gomp/;>OpenMP
   
+
+  The https://gcc.gnu.org/onlinedocs/libgomp/;>GNU Offloading and
+  Multi Processing Runtime Library Manual has been updated and extended,
+  improving especially the description of ICVs, memory allocation, environment variables and OpenMP
+  routines.
+
 
   The requires directive's unified_address
   requirement is now fulfilled by both AMD GCN and nvptx devices.
   AMD GCN and nvptx devices now support low-latency allocators as
   https://gcc.gnu.org/onlinedocs/libgomp/Offload-Target-Specifics.html;
   >detailed in the manual. Initial support for pinned-memory
-  allocators has been added (https://gcc.gnu.org/onlinedocs/libgomp/Memory-allocation.html;
-  >as detailed in the manual)
+  allocators has been added and, on Linux,
+  https://github.com/numactl/numactl;>libnuma is now used
+  for allocators requesting the nearest-partition trait (both is described
+  in the https://gcc.gnu.org/onlinedocs/libgomp/Memory-allocation.html;
+  >memory allocation section of the manual).
 
 OpenMP 5.0: The allocate directive is now
   supported for stack variables in C and Fortran, including the OpenMP 5.1
@@ -74,8 +84,8 @@ a work-in-progress.
   using present as map-type modifier and in
   defaultmap. The indirect clause is now supported
   for C and C++.  The performance of copying strided data from or to nvptx
-  devices using the OpenMP 5.1 routine omp_target_memcpy_rect
-  has been improved.
+  and AMD GPU devices using the OpenMP 5.1 routine
+  omp_target_memcpy_rect has been improved.
 
 
   OpenMP 5.2: The OMP_TARGET_OFFLOAD=mandatory handling has
@@ -83,23 +93,14 @@ a work-in-progress.
   For Fortran, the list of directives permitted in Fortran pure procedures
   was extended. Additionally, the spec change has been implemented for
   default implicit mapping of C/C++ pointers pointing to unmapped storage.
-  The destroy now optionally accepts the depend object as
-  argument.
+  The destroy clause now optionally accepts the depend object
+  as argument.
 
 
   OpenMP 6.0 preview (TR11/TR12): The decl attribute is now
   supported in C++ 11 and the directive, sequence
   and decl attributes are now supported in C 23.
 
-
-  The https://gcc.gnu.org/onlinedocs/libgomp/;>GNU Offloading and
-  Multi Processing Runtime Library Manual has been updated and extended,
-  improving especially the description of ICVs, memory allocation, environment variables and OpenMP
-  routines. On Linux, https://github.com/numactl/numactl;>libnuma
-  is now used for allocators requesting the nearest-partition trait as
-  detailed in the manual.
-
   
   
   https://gcc.gnu.org/wiki/OpenACC;>OpenACC

Re: [wwwdocs] gcc-14/changes.html: OpenMP - improve wording

[Martin Jambor]

Hi Tobias,

On Mon, Jan 08 2024, Tobias Burnus wrote:
> The attached patch

there was no patch attached to your message.

Martin

> does a tiny updated to the OpenMP features (AMD GCN 
> now also has an optimized memcpy_rect not only nvptx), but the main 
> change is some shifting around to make it more consistent and better 
> readable.
>
> I intend to commit this relatively soon; like always, comments and 
> suggestions are welcome - be it before or after the commit.
>
> Current version: http://gcc.gnu.org/gcc-14/changes.html
>
> Thanks,
>
> Tobias

[wwwdocs][PATCH] gcc-14/changes: Update APX inline asm behavior for x86_64

[Hongyu Wang]

Hi,

This patch adds missing description for inline asm behavior and related
compiler switch for APX.

Ok for gcc-wwwdocs?

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

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index e3a68998..73a90d30 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -342,6 +342,12 @@ a work-in-progress.
   NDD, PPX and PUSH2POP2. APX support is available via the
   -mapxf compiler switch.
   
+  For inline asm support with APX, by default the EGPR feature was
+  disabled to prevent potential illegal instruction with EGPR occurs.
+  To invoke egpr usage in inline asm, use new compiler option
+  -mapx-inline-asm-use-gpr32 and user should ensure the instruction
+  supports EGPR.
+  
   New ISA extension support for Intel AVX10.1 was added.
   AVX10.1 intrinsics are available via the -mavx10.1 or
   -mavx10.1-256 compiler switch with 256-bit vector size
-- 
2.31.1

[wwwdocs] gcc-14/changes.html: OpenMP - improve wording

[Tobias Burnus]

The attached patch does a tiny updated to the OpenMP features (AMD GCN 
now also has an optimized memcpy_rect not only nvptx), but the main 
change is some shifting around to make it more consistent and better 
readable.


I intend to commit this relatively soon; like always, comments and 
suggestions are welcome - be it before or after the commit.


Current version: http://gcc.gnu.org/gcc-14/changes.html

Thanks,

Tobias

Re: [PATCH wwwdocs 1/1] gcc-14: document P1689R5 scanning output support

[Arsen Arsenović]

Hi Ben,

Ben Boeckel  writes:

> Ping? Is this the right place to submit this patch?

Yes, this is the correct list, though it is usually recommended to use
--subject-prefix='PATCH wwwdocs' or such, to catch the right eyes.  See:
https://gcc.gnu.org/contribute.html#webchanges

I've added it to my subject, hopefully that works.

Have a lovely day!
--
Arsen Arsenović


signature.asc
Description: PGP signature

RE: [gcc-wwwdocs PATCH v2] gcc-13/14: Mention recent update for x86_64 backend

[Jiang, Haochen]

> -Original Message-
> From: Haochen Jiang 
> Sent: Thursday, December 21, 2023 4:26 PM
> To: gcc-patches@gcc.gnu.org
> Cc: ubiz...@gmail.com; Liu, Hongtao ;
> ger...@pfeifer.com
> Subject: [gcc-wwwdocs PATCH v2] gcc-13/14: Mention recent update for
> x86_64 backend
> 
> Hi all,
> 
> This is the v2 patch for the wwwdocs change regarding to review.
> 
> If there is no objection, I will push this change next Tuesday.

I will commit the doc change patch.

Thx,
Haochen

> 
> Changes is v2:
> 
>   - Remove RAO-INT from Grand Ridge
>   - Remove the mask register restriction for -mno-evex512
>   - Arrange the options alphabetically
>   - Other minor text change
> 
> Thx,
> Haochen
> 
> Messages in v1:
> 
> This patch will mention the following changes in wwwdocs for x86_64
> backend:
> 
>   - AVX10.1 support
>   - APX EGPR, PUSH2POP2, PPX and NDD support
>   - Xeon Phi ISAs deprecated
> 
> Also I adjust the words in x86_64 part for GCC 13.
> 
> ---
> Mention AVX10.1 support, APX support and Xeon Phi deprecate in GCC 14.
> Also adjust documentation in GCC 13.
> ---
>  htdocs/gcc-13/changes.html | 38 --
>  htdocs/gcc-14/changes.html | 27 ++-
>  2 files changed, 42 insertions(+), 23 deletions(-)
> 
> diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index
> d3bacc16..b4b1a39a 100644
> --- a/htdocs/gcc-13/changes.html
> +++ b/htdocs/gcc-13/changes.html
> @@ -543,24 +543,28 @@ You may also want to check out our
>__bf16 type to x86 psABI. Users need to adjust their
>AVX512BF16-related source code when upgrading GCC12 to GCC13.
>
> -  New ISA extension support for Intel AVX-IFMA was added.
> -  AVX-IFMA intrinsics are available via the -mavxifma
> +  New ISA extension support for Intel AMX-COMPLEX was added.
> +  AMX-COMPLEX intrinsics are available via the
> + -mamx-complex
>compiler switch.
>
> -  New ISA extension support for Intel AVX-VNNI-INT8 was added.
> -  AVX-VNNI-INT8 intrinsics are available via the -
> mavxvnniint8
> +  New ISA extension support for Intel AMX-FP16 was added.
> +  AMX-FP16 intrinsics are available via the -mamx-fp16
> +  compiler switch.
> +  
> +  New ISA extension support for Intel AVX-IFMA was added.
> +  AVX-IFMA intrinsics are available via the -mavxifma
>compiler switch.
>
>New ISA extension support for Intel AVX-NE-CONVERT was added.
>AVX-NE-CONVERT intrinsics are available via the
>-mavxneconvert compiler switch.
>
> -  New ISA extension support for Intel CMPccXADD was added.
> -  CMPccXADD intrinsics are available via the -mcmpccxadd
> +  New ISA extension support for Intel AVX-VNNI-INT8 was added.
> +  AVX-VNNI-INT8 intrinsics are available via the
> + -mavxvnniint8
>compiler switch.
>
> -  New ISA extension support for Intel AMX-FP16 was added.
> -  AMX-FP16 intrinsics are available via the -mamx-fp16
> +  New ISA extension support for Intel CMPccXADD was added.
> +  CMPccXADD intrinsics are available via the
> + -mcmpccxadd
>compiler switch.
>
>New ISA extension support for Intel PREFETCHI was added.
> @@ -571,10 +575,6 @@ You may also want to check out our
>RAO-INT intrinsics are available via the -mraoint
>compiler switch.
>
> -  New ISA extension support for Intel AMX-COMPLEX was added.
> -  AMX-COMPLEX intrinsics are available via the -mamx-
> complex
> -  compiler switch.
> -  
>GCC now supports the Intel CPU named Raptor Lake through
>  -march=raptorlake.
>  Raptor Lake is based on Alder Lake.
> @@ -585,13 +585,13 @@ You may also want to check out our
>
>GCC now supports the Intel CPU named Sierra Forest through
>  -march=sierraforest.
> -The switch enables the AVX-IFMA, AVX-VNNI-INT8, AVX-NE-CONVERT,
> CMPccXADD,
> -ENQCMD and UINTR ISA extensions.
> +Based on ISA extensions enabled on Alder Lake, the switch further enables
> +the AVX-IFMA, AVX-NE-CONVERT, AVX-VNNI-INT8, CMPccXADD,
> ENQCMD and UINTR
> +ISA extensions.
>
>GCC now supports the Intel CPU named Grand Ridge through
>  -march=grandridge.
> -The switch enables the AVX-IFMA, AVX-VNNI-INT8, AVX-NE-CONVERT,
> CMPccXADD,
> -ENQCMD, UINTR and RAO-INT ISA extensions.
> +Grand Ridge is based on Sierra Forest.
>
>GCC now supports the Intel CPU named Emerald Rapids through
>  -march=emeraldrapids.
> @@ -599,11 +599,13 @@ You may also want to check out our
>
>GCC now supports the Intel CPU named Granite Rapids through
>  

[gcc-wwwdocs PATCH v2] gcc-13/14: Mention recent update for x86_64 backend

[Haochen Jiang]

Hi all,

This is the v2 patch for the wwwdocs change regarding to review.

If there is no objection, I will push this change next Tuesday.

Changes is v2:

  - Remove RAO-INT from Grand Ridge
  - Remove the mask register restriction for -mno-evex512
  - Arrange the options alphabetically
  - Other minor text change

Thx,
Haochen

Messages in v1:

This patch will mention the following changes in wwwdocs for x86_64 backend:

  - AVX10.1 support
  - APX EGPR, PUSH2POP2, PPX and NDD support
  - Xeon Phi ISAs deprecated

Also I adjust the words in x86_64 part for GCC 13.

---
Mention AVX10.1 support, APX support and Xeon Phi deprecate in GCC 14.
Also adjust documentation in GCC 13.
---
 htdocs/gcc-13/changes.html | 38 --
 htdocs/gcc-14/changes.html | 27 ++-
 2 files changed, 42 insertions(+), 23 deletions(-)

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index d3bacc16..b4b1a39a 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -543,24 +543,28 @@ You may also want to check out our
   __bf16 type to x86 psABI. Users need to adjust their
   AVX512BF16-related source code when upgrading GCC12 to GCC13.
   
-  New ISA extension support for Intel AVX-IFMA was added.
-  AVX-IFMA intrinsics are available via the -mavxifma
+  New ISA extension support for Intel AMX-COMPLEX was added.
+  AMX-COMPLEX intrinsics are available via the -mamx-complex
   compiler switch.
   
-  New ISA extension support for Intel AVX-VNNI-INT8 was added.
-  AVX-VNNI-INT8 intrinsics are available via the -mavxvnniint8
+  New ISA extension support for Intel AMX-FP16 was added.
+  AMX-FP16 intrinsics are available via the -mamx-fp16
+  compiler switch.
+  
+  New ISA extension support for Intel AVX-IFMA was added.
+  AVX-IFMA intrinsics are available via the -mavxifma
   compiler switch.
   
   New ISA extension support for Intel AVX-NE-CONVERT was added.
   AVX-NE-CONVERT intrinsics are available via the
   -mavxneconvert compiler switch.
   
-  New ISA extension support for Intel CMPccXADD was added.
-  CMPccXADD intrinsics are available via the -mcmpccxadd
+  New ISA extension support for Intel AVX-VNNI-INT8 was added.
+  AVX-VNNI-INT8 intrinsics are available via the -mavxvnniint8
   compiler switch.
   
-  New ISA extension support for Intel AMX-FP16 was added.
-  AMX-FP16 intrinsics are available via the -mamx-fp16
+  New ISA extension support for Intel CMPccXADD was added.
+  CMPccXADD intrinsics are available via the -mcmpccxadd
   compiler switch.
   
   New ISA extension support for Intel PREFETCHI was added.
@@ -571,10 +575,6 @@ You may also want to check out our
   RAO-INT intrinsics are available via the -mraoint
   compiler switch.
   
-  New ISA extension support for Intel AMX-COMPLEX was added.
-  AMX-COMPLEX intrinsics are available via the -mamx-complex
-  compiler switch.
-  
   GCC now supports the Intel CPU named Raptor Lake through
 -march=raptorlake.
 Raptor Lake is based on Alder Lake.
@@ -585,13 +585,13 @@ You may also want to check out our
   
   GCC now supports the Intel CPU named Sierra Forest through
 -march=sierraforest.
-The switch enables the AVX-IFMA, AVX-VNNI-INT8, AVX-NE-CONVERT, CMPccXADD,
-ENQCMD and UINTR ISA extensions.
+Based on ISA extensions enabled on Alder Lake, the switch further enables
+the AVX-IFMA, AVX-NE-CONVERT, AVX-VNNI-INT8, CMPccXADD, ENQCMD and UINTR
+ISA extensions.
   
   GCC now supports the Intel CPU named Grand Ridge through
 -march=grandridge.
-The switch enables the AVX-IFMA, AVX-VNNI-INT8, AVX-NE-CONVERT, CMPccXADD,
-ENQCMD, UINTR and RAO-INT ISA extensions.
+Grand Ridge is based on Sierra Forest.
   
   GCC now supports the Intel CPU named Emerald Rapids through
 -march=emeraldrapids.
@@ -599,11 +599,13 @@ You may also want to check out our
   
   GCC now supports the Intel CPU named Granite Rapids through
 -march=graniterapids.
-The switch enables the AMX-FP16 and PREFETCHI ISA extensions.
+Based on Sapphire Rapids, the switch further enables the AMX-FP16 and
+PREFETCHI ISA extensions.
   
   GCC now supports the Intel CPU named Granite Rapids D through
 -march=graniterapids-d.
-The switch enables the AMX-FP16, PREFETCHI and AMX-COMPLEX ISA extensions.
+Based on Granite Rapids, the switch further enables the AMX-COMPLEX ISA
+extensions.
   
   GCC now supports AMD CPUs based on the znver4 core
 via -march=znver4.  The switch makes GCC consider
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 24e6409a..4b83037a 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -320,8 +320,18 @@ a work-in-progress.
 IA-32/x86-64
 
   New compiler option -m[no-]evex512 was added.
-  The compiler switch enables/disables 512 bit vector and 64 bit mask
-  register

[PATCH, wwwdocs] RISC-V: Add -mcmodel=large for GCC-14

[Palmer Dabbelt]

This was just merged.  Looks like we forgot to add any other NEWS items,
so I've added the header as well.
---
 htdocs/gcc-14/changes.html | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 24e6409a..2a7432a7 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -395,7 +395,11 @@ a work-in-progress.
 
 
 
-
+RISC-V
+
+
+  Support for -mcmodel=large has been added.
+
 
 
 
-- 
2.43.0

[committed][gcc-wwwdocs] Add blurb about bitfield signedness on mcore

[Jeff Law]

Pushed to the trunk.

jeffcommit e56dc0003729ea6f7d26594dae34d218543edb49
Author: Jeff Law 
Date:   Tue Dec 19 21:28:03 2023 -0700

Document that bitfields are signed on mcore now.

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index eb14e09d..11c7ca7e 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -341,6 +341,13 @@ a work-in-progress.
   
 
 
+
+
+  Bitfields are now signed by default per GCC policy.  If you need 
bitfields
+to be unsigned, then use -funsigned-bitfields
+  
+
+
 
 
 

[wwwdocs] Update notes on libstdc++ header dependency changes in GCC 14

[Jonathan Wakely]

Pushed to wwwdocs.

-- >8 --

---
 htdocs/gcc-14/porting_to.html | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/htdocs/gcc-14/porting_to.html b/htdocs/gcc-14/porting_to.html
index dea9ac80..3e4cedc3 100644
--- a/htdocs/gcc-14/porting_to.html
+++ b/htdocs/gcc-14/porting_to.html
@@ -38,10 +38,14 @@ be included explicitly when compiling with GCC 14:
 
 
  algorithm
-  (for std::copy_n, std::lower_bound,
+  (for std::copy_n, std::find_if,
+  std::lower_bound,
   std::remove, std::reverse,
   std::sort etc.)
 
+ cstdint
+  (for std::int8_t, std::int32_t etc.)
+
 
 
 
-- 
2.43.0

[wwwdocs] Document std::print and std::ranges::to for C++23

[Jonathan Wakely]

Pushed to wwwdocs.

-- >8 --

---
 htdocs/gcc-14/changes.html | 12 +---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 346785a0..eb14e09d 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -209,8 +209,14 @@ a work-in-progress.
   
   Improved experimental support for C++23, including:
 
+The std::ranges::to function for converting
+  ranges to containers.
+
 The stacktrace header is supported by default.
 
+std::print and std::println
+  (requires linking with -lstdc++exp on Windows).
+
 Formatters for std::thread::id and
   std::stacktrace.
 
@@ -237,12 +243,12 @@ a work-in-progress.
 std::numeric_limits_Float64 are now defined
 for all standard modes, not only for C++23.
   
-  Using the std::setfill manipulator with
-std::istream is deprecated.
-  
   Added missing functions for float and
 long double to cmath.
   
+  Using the std::setfill manipulator with
+std::istream is deprecated.
+  
 
 
 
-- 
2.43.0

[pushed] wwwdocs: projects/cli: Update ECMA reference

[Gerald Pfeifer]

Gerald

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

diff --git a/htdocs/projects/cli.html b/htdocs/projects/cli.html
index 394832b6..47ddb362 100644
--- a/htdocs/projects/cli.html
+++ b/htdocs/projects/cli.html
@@ -460,7 +460,7 @@ allowing the user to provide a native implementation if 
necessary.
 [1] wwwdocs:
 
 
-ECMA, https://www.ecma-international.org/publications-and-standards/standards/ecma-335/;>
+ECMA, https://ecma-international.org/publications-and-standards/standards/ecma-335/;>
 Common Language Infrastructure (CLI), 4th edition, June 2006.
 
 
-- 
2.43.0

[wwwdocs][patch] gcc-14/changes.html + project/gomp/: Update OpenMP status

[Tobias Burnus]

Attached is an in-between update for the release notes and also for the project 
status page.

The latter contains an implementation-status page that is updated based on the 
libgomp.texi entries;
I think there are more issues, but I found an incomplete update which is now 
fixed. I probably need to
go through that list and check it again.

Comments, suggestions, remarks before (or after) I commit it?

Tobias

PS: I hope that we can still review, revise, commit some more pending patches
(in general, but mostly talking about OpenMP, OpenACC and nvptx/gcn here).

PPS: I or someone else also needs to update the Fortran part, now that there is
-std=f2023 (besides -std=c23 and -std=c++23). I have not checked for additional
features.
-
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 
München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas 
Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht 
München, HRB 106955
gcc-14/changes.html + project/gomp/: Update OpenMP status

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index c49c13e9..516f3954 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -52,10 +53,22 @@ a work-in-progress.
 
   The requires directive's unified_address
   requirement is now fulfilled by both AMD GCN and nvptx devices.
+  AMD GCN and nvptx devices now support low-latency allocators as
+  https://gcc.gnu.org/onlinedocs/libgomp/Offload-Target-Specifics.html;
+  >detailed in the manual. Initial support for pinned-memory
+  allocators has been added (https://gcc.gnu.org/onlinedocs/libgomp/Memory-allocation.html;
+  >as detailed in the manual)
 
 OpenMP 5.0: The allocate directive is now
   supported for stack variables in C and Fortran, including the OpenMP 5.1
-  align modifier.
+  align modifier. For Fortran, OpenMP allocators can now be
+  used for allocatables and pointers using the allocate
+  directive and its OpenMP 5.2 replacement, the allocators
+  directive; files using this allocator and all files that might directly
+  or indirectly (intrinisic assignment, intent(out), ...)
+  de- or reallocate such-allocated variables must be compiled with the
+  https://gcc.gnu.org/onlinedocs/gfortran/Fortran-Dialect-Options.html#index-fopenmp-allocators;
+  >-fopenmp-allocators option.
 
 
   OpenMP 5.1: Support was added for collapsing imperfectly nested loops and

diff --git a/htdocs/projects/gomp/index.html b/htdocs/projects/gomp/index.html
index 03f74a88..bf20bb88 100644
--- a/htdocs/projects/gomp/index.html
+++ b/htdocs/projects/gomp/index.html
@@ -480,7 +480,7 @@ than listed, depending on resolved corner cases and optimizations.
   
 allocate directive
 GCC14
-Only C and Fortran, only stack variables
+Only C for stack/automatic and Fortran for stack/automatic and allocatable/pointer variables
   
   
 Discontiguous array section with target update construct
@@ -555,7 +555,7 @@ than listed, depending on resolved corner cases and optimizations.
   
 align clause in allocate directive
 GCC14
-Only C and Fortran (and only stack variables)
+Only C and Fortran (and not for static variables)
   
   
 align modifier in allocate clause
@@ -820,10 +820,15 @@ than listed, depending on resolved corner cases and optimizations.
 
   
   
-Deprecation of no-argument destroy clause on depobj
+destroy clause with destroy-var argument on depobj
 GCC14
 
   
+  
+Deprecation of no-argument destroy clause on depobj
+No
+
+  
   
 linear clause syntax changes and step modifier
 GCC13

RE: [gcc-wwwdocs PATCH] gcc-13/14: Mention recent update for x86_64 backend

[Jiang, Haochen]

> -Original Message-
> From: Gerald Pfeifer 
> Sent: Wednesday, December 13, 2023 2:20 PM
> To: Jiang, Haochen 
> Cc: gcc-patches@gcc.gnu.org; Liu, Hongtao ;
> ubiz...@gmail.com
> Subject: Re: [gcc-wwwdocs PATCH] gcc-13/14: Mention recent update for
> x86_64 backend
> 
> On Fri, 8 Dec 2023, Haochen Jiang wrote:
> > +++ b/htdocs/gcc-13/changes.html
> 
> > +Based on ISA extensions enabled on Alder Lake, the switch further
> enables
> > +the AVX-IFMA, AVX-VNNI-INT8, AVX-NE-CONVERT, CMPccXADD,
> ENQCMD and UINTR
> > +ISA extensions.
> 
> Personally I would alphabetically sort all the options, like you have mostly
> done already. Just AVX-VNNI-INT8 and AVX-NE-CONVERT are not.
> 
> (Maybe you have a reason, and in any case this should not block this
> patch.)
> 
> 
> > +++ b/htdocs/gcc-14/changes.html
> > +  New ISA extension support for Intel AVX10.1 was added.
> > +  AVX10.1 intrinsics are available via the -mavx10.1 or
> > +  -mavx10.1-256 compiler switch with 256 bit vector size
> > +  support. 512 bit vector size support for AVX10.1 intrinsics are
> 
> We usually write 256-bit and 512-bit as adjectives, cf.
> gcc.gnu.org/codingconventions.html .
> 
> > +  Part of new feature support for Intel APX was added, including EGPR,
> > +  PUSH2POP2, PPX and NDD.
> 
> Alphabetically?
> 
> > APX features are available via the
> > +  -mapxf compiler switch.
> 
> Could we say "APX is enabled via..." or "APX support is available via..."?
> 
> > +  Xeon Phi CPUs support (a.k.a. Knight Landing and Knight Mill) are
> marked
> > +as deprecated. GCC will emit a warning when using the
> > +-mavx5124fmaps, -mavx5124vnniw,
> > +-mavx512er, -mavx512pf,
> > +-mprefetchwt1, -march=knl,
> > +-march=knm, -mtune=knl and -
> mtune=knm
> > +compiler switch. The support will be removed in GCC 15.
> > +  
> 
> I believe "or" instead of "and" will be clearer.
> 
> And "compiler switches" (plural).
> 
> And just "Support" in the last sentence.
> 
> 
> Thanks for submitting these! No need for further review before committing
> (a minor variation).

Thanks for your review. I will fix them and also other alphabetic issue in 
GCC13/14
doc. Since there will be a Grand Ridge ISA change coming soon in GCC13 (I have
not sent out the patch but will happen within one week), I will commit the whole
patch after that landed.

Thx,
Haochen

> 
> Gerald

Re: [gcc-wwwdocs PATCH] gcc-13/14: Mention recent update for x86_64 backend

[Gerald Pfeifer]

On Fri, 8 Dec 2023, Haochen Jiang wrote:
> +++ b/htdocs/gcc-13/changes.html

> +Based on ISA extensions enabled on Alder Lake, the switch further enables
> +the AVX-IFMA, AVX-VNNI-INT8, AVX-NE-CONVERT, CMPccXADD, ENQCMD and UINTR
> +ISA extensions.

Personally I would alphabetically sort all the options, like you have 
mostly done already. Just AVX-VNNI-INT8 and AVX-NE-CONVERT are not.

(Maybe you have a reason, and in any case this should not block this 
patch.)


> +++ b/htdocs/gcc-14/changes.html
> +  New ISA extension support for Intel AVX10.1 was added.
> +  AVX10.1 intrinsics are available via the -mavx10.1 or
> +  -mavx10.1-256 compiler switch with 256 bit vector size
> +  support. 512 bit vector size support for AVX10.1 intrinsics are

We usually write 256-bit and 512-bit as adjectives, cf. 
gcc.gnu.org/codingconventions.html .

> +  Part of new feature support for Intel APX was added, including EGPR,
> +  PUSH2POP2, PPX and NDD. 

Alphabetically?

> APX features are available via the
> +  -mapxf compiler switch.

Could we say "APX is enabled via..." or "APX support is available via..."?

> +  Xeon Phi CPUs support (a.k.a. Knight Landing and Knight Mill) are 
> marked
> +as deprecated. GCC will emit a warning when using the
> +-mavx5124fmaps, -mavx5124vnniw,
> +-mavx512er, -mavx512pf,
> +-mprefetchwt1, -march=knl,
> +-march=knm, -mtune=knl and 
> -mtune=knm
> +compiler switch. The support will be removed in GCC 15.
> +  

I believe "or" instead of "and" will be clearer.

And "compiler switches" (plural).

And just "Support" in the last sentence.


Thanks for submitting these! No need for further review before committing
(a minor variation).

Gerald

RE: [PATCH] [gcc-wwwdocs]gcc-13/14: Mention Intel new ISA and march support

[Gerald Pfeifer]

On Mon, 27 Nov 2023, Jiang, Haochen wrote:
>> How about changing this to use "and", as in
>>   "The switch enables the AMX-FP16, PREFETCHI ISA extensions."
>> ?
> Ok for me.

Done and pushed thusly.

Gerald


commit 617a25d7d89a9cce121e85b693eed1ee3f94354b
Author: Gerald Pfeifer 
Date:   Wed Dec 13 13:43:39 2023 +0800

gcc-13: Refine noteo on -march=graniterapids

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 8ef3d639..ee6383a0 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -593,7 +593,7 @@ You may also want to check out our
   
   GCC now supports the Intel CPU named Granite Rapids through
 -march=graniterapids.
-The switch enables the AMX-FP16, PREFETCHI ISA extensions.
+The switch enables the AMX-FP16 and PREFETCHI ISA extensions.
   
   GCC now supports the Intel CPU named Granite Rapids D through
 -march=graniterapids-d.

[gcc-wwwdocs COMMITTED] Disallow /cgit for web robots

[Mark Wielaard]

Although cgit is more efficient than gitweb it still is not great
for bots to go through it.
---
 htdocs/robots.txt | 1 +
 1 file changed, 1 insertion(+)

diff --git a/htdocs/robots.txt b/htdocs/robots.txt
index c650057b..b9fc830d 100644
--- a/htdocs/robots.txt
+++ b/htdocs/robots.txt
@@ -6,6 +6,7 @@ User-agent: *
 Disallow: /viewvc/
 Disallow: /viewcvs
 Disallow: /git/
+Disallow: /cgit/
 Disallow: /svn
 Disallow: /cgi-bin/
 Disallow: /bugzilla/buglist.cgi
-- 
2.39.3

[gcc-wwwdocs PATCH] gcc-13/14: Mention recent update for x86_64 backend

[Haochen Jiang]

Hi all,

This patch will mention the following changes in wwwdocs for x86_64 backend:

  - AVX10.1 support
  - APX EGPR, PUSH2POP2, PPX and NDD support
  - Xeon Phi ISAs deprecated

Also I adjust the words in x86_64 part for GCC 13. Ok for gcc-wwwdocs?

Thx,
Haochen

Mention AVX10.1 support, APX support and Xeon Phi deprecate in GCC 14.
Also adjust documentation in GCC 13.
---
 htdocs/gcc-13/changes.html | 14 --
 htdocs/gcc-14/changes.html | 18 ++
 2 files changed, 26 insertions(+), 6 deletions(-)

diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 8ef3d639..e29ca72e 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -579,13 +579,13 @@ You may also want to check out our
   
   GCC now supports the Intel CPU named Sierra Forest through
 -march=sierraforest.
-The switch enables the AVX-IFMA, AVX-VNNI-INT8, AVX-NE-CONVERT, CMPccXADD,
-ENQCMD and UINTR ISA extensions.
+Based on ISA extensions enabled on Alder Lake, the switch further enables
+the AVX-IFMA, AVX-VNNI-INT8, AVX-NE-CONVERT, CMPccXADD, ENQCMD and UINTR
+ISA extensions.
   
   GCC now supports the Intel CPU named Grand Ridge through
 -march=grandridge.
-The switch enables the AVX-IFMA, AVX-VNNI-INT8, AVX-NE-CONVERT, CMPccXADD,
-ENQCMD, UINTR and RAO-INT ISA extensions.
+Based on Sierra Forest, the switch further enables RAO-INT ISA extensions.
   
   GCC now supports the Intel CPU named Emerald Rapids through
 -march=emeraldrapids.
@@ -593,11 +593,13 @@ You may also want to check out our
   
   GCC now supports the Intel CPU named Granite Rapids through
 -march=graniterapids.
-The switch enables the AMX-FP16, PREFETCHI ISA extensions.
+Based on Sapphire Rapids, the switch further enables the AMX-FP16 and
+PREFETCHI ISA extensions.
   
   GCC now supports the Intel CPU named Granite Rapids D through
 -march=graniterapids-d.
-The switch enables the AMX-FP16, PREFETCHI and AMX-COMPLEX ISA extensions.
+Based on Granite Rapids, the switch further enables the AMX-COMPLEX ISA
+extensions.
   
   GCC now supports AMD CPUs based on the znver4 core
 via -march=znver4.  The switch makes GCC consider
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 6d7138f8..8590f735 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -296,6 +296,16 @@ a work-in-progress.
   USER_MSR intrinsics are available via the -muser_msr
   compiler switch.
   
+  New ISA extension support for Intel AVX10.1 was added.
+  AVX10.1 intrinsics are available via the -mavx10.1 or
+  -mavx10.1-256 compiler switch with 256 bit vector size
+  support. 512 bit vector size support for AVX10.1 intrinsics are
+  available via the -mavx10.1-512 compiler switch.
+  
+  Part of new feature support for Intel APX was added, including EGPR,
+  PUSH2POP2, PPX and NDD. APX features are available via the
+  -mapxf compiler switch.
+  
   GCC now supports the Intel CPU named Clearwater Forest through
 -march=clearwaterforest.
 Based on Sierra Forest, the switch further enables the AVX-VNNI-INT16,
@@ -321,6 +331,14 @@ a work-in-progress.
 Based on Arrow Lake S, the switch further enables the PREFETCHI ISA
 extensions.
   
+  Xeon Phi CPUs support (a.k.a. Knight Landing and Knight Mill) are marked
+as deprecated. GCC will emit a warning when using the
+-mavx5124fmaps, -mavx5124vnniw,
+-mavx512er, -mavx512pf,
+-mprefetchwt1, -march=knl,
+-march=knm, -mtune=knl and 
-mtune=knm
+compiler switch. The support will be removed in GCC 15.
+  
 
 
 
-- 
2.31.1

[PATCH] wwwdocs: spelling mistakes

[Jonny Grant]

2023-12-03  Jonathan Grant  

htdocs/
* bugs/management.html: adition spelling.
* codingrationale.html: suprises spelling.
* contribute.html: elipsis leter spelling.
* gcc-14/changes.html: modifed spelling.
* gccmission.html: groundrules spelling.
* projects/cli.html: backnend  spelling.
* projects/cfg.html: nowday spelling.
* projects/cxx-reflection/index.html: fonctionalities spelling.
* projects/optimize.html: blowup -> increase, indepentent spelling.
* projects/tree-profiling.html: Optimizaion spelling.
* testing/index.html: runing spelling.



>From 97f197c3f8218df2362a053d47548f27cd19d81a Mon Sep 17 00:00:00 2001
From: Jonathan Grant 
Date: Sun, 3 Dec 2023 00:29:43 +
Subject: [PATCH] wwwdocs: spelling mistake corrections

---
 htdocs/bugs/management.html   | 2 +-
 htdocs/codingrationale.html   | 2 +-
 htdocs/contribute.html| 4 ++--
 htdocs/gcc-14/changes.html| 2 +-
 htdocs/gccmission.html| 2 +-
 htdocs/projects/cfg.html  | 2 +-
 htdocs/projects/cli.html  | 2 +-
 htdocs/projects/cxx-reflection/index.html | 2 +-
 htdocs/projects/optimize.html | 6 +++---
 htdocs/projects/tree-profiling.html   | 2 +-
 htdocs/testing/index.html | 2 +-
 11 files changed, 14 insertions(+), 14 deletions(-)

diff --git a/htdocs/bugs/management.html b/htdocs/bugs/management.html
index 28dfa76a..b2bb740e 100644
--- a/htdocs/bugs/management.html
+++ b/htdocs/bugs/management.html
@@ -64,7 +64,7 @@ perspective, these are the relevant ones and what their 
values mean:
 The status and resolution fields define and track the life cycle of a
 bug.  In addition to their https://gcc.gnu.org/bugzilla/page.cgi?id=fields.html;>regular
-descriptions, we also use two adition status values:
+descriptions, we also use two additional status values:
 
 
 
diff --git a/htdocs/codingrationale.html b/htdocs/codingrationale.html
index 6cc76885..c51c9da4 100644
--- a/htdocs/codingrationale.html
+++ b/htdocs/codingrationale.html
@@ -155,7 +155,7 @@ Wide use of implicit conversion can cause some very 
surprising results.
 
 
 C++03 has no explicit conversion operators,
-and hence using them cannot avoid suprises.
+and hence using them cannot avoid surprises.
 Wait for C++11.
 
 
diff --git a/htdocs/contribute.html b/htdocs/contribute.html
index fbe5b39c..152675fa 100644
--- a/htdocs/contribute.html
+++ b/htdocs/contribute.html
@@ -329,7 +329,7 @@ the commit message so that Bugzilla will correctly notice 
the
 commit.  If your patch relates to two bugs, then write
 [PRn, PRm].  For multiple
 bugs, just cite the most relevant one in the summary and use an
-elipsis instead of the second, or subsequent PR numbers; list all the
+ellipsis instead of the second, or subsequent PR numbers; list all the
 related PRs in the body of the commit message in the normal way.
 
 It is not necessary to cite bugs that are closed as duplicates of
@@ -354,7 +354,7 @@ together.
 If you submit a new version of a patch series, then you should
 start a new email thread (don't reply to the original patch series).
 This avoids email threads becoming confused between discussions of the
-first and subsequent revisions of the patch set.  Your cover leter
+first and subsequent revisions of the patch set.  Your cover letter
 (0/nnn) should explain clearly what has been changed between
 the two patch series.  Also state if some of the patches are unchanged
 between revisions; this saves maintainers having to re-review the
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 5a453437..bd51ecb4 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -34,7 +34,7 @@ a work-in-progress.
   another structure, is deprecated. Refer to
   https://gcc.gnu.org/onlinedocs/gcc/Zero-Length.html;>
   Zero Length Arrays.
-  Any code relying on this extension should be modifed to ensure that
+  Any code relying on this extension should be modified to ensure that
   C99 flexible array members only end up at the ends of structures.
   Please use the warning option
   https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wflex-array-member-not-at-end;>-Wflex-array-member-not-at-end
 to
diff --git a/htdocs/gccmission.html b/htdocs/gccmission.html
index 58a12755..1124fe9f 100644
--- a/htdocs/gccmission.html
+++ b/htdocs/gccmission.html
@@ -55,7 +55,7 @@ GCC.
  Patches will be considered equally based on their
  technical merits.
  All individuals and companies are welcome to contribute
- as long as they accept the groundrules.
+ as long as they accept the ground rules.
  
 Open mailing lists.
 Developer friendly tools and procedures (i.e. [version control], multiple
diff --git a/htdocs/projects/cfg.html b/htdocs/projects/cfg.html
index b1ee1f34..b695766e 1006

[pushed] wwwdocs: benchmarks: Remove http://annwm.lbl.gov/bench/

[Gerald Pfeifer]

This has been unreachable for months (at least).

If any of you is aware of some other link to add to
https://gcc.gnu.org/benchmarks/ please let me know.

Gerald
---
 htdocs/benchmarks/index.html | 7 ---
 1 file changed, 7 deletions(-)

diff --git a/htdocs/benchmarks/index.html b/htdocs/benchmarks/index.html
index 6ccee355..ee3a2161 100644
--- a/htdocs/benchmarks/index.html
+++ b/htdocs/benchmarks/index.html
@@ -47,13 +47,6 @@ Environment (CSiBE), along with the testbed and 
measurement scripts.
 
 Related benchmarks and scripts
 
-
-Charles Leggett runs several benchmarks (Bench++, Haney, Stepanov, OOPACK)
-comparing various versions of GCC and KAI KCC with several optimization
-levels.  Results can be found at http://annwm.lbl.gov/bench/;>
-http://annwm.lbl.gov/bench/.
-
-
 
 SUSE runs various other C++ benchmarks and Polyhedron.
 Results can be found at https://gcc.opensuse.org;
-- 
2.43.0

[pushed] wwwdocs: conduct: Change further creativecommons.org links to https

[Gerald Pfeifer]

This feels a bit lick whack-a-mole to me, though I am hopefull to now have 
caught and covered all cases where your CoC pages link to addresses that 
permanently redirect.

Famous last words. :-)

(The redirect work, avoiding them primarily helps us to find "odd" cases.
The extra turnaround should be hardly noticable for most.)

Gerald

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

diff --git a/htdocs/conduct-faq.html b/htdocs/conduct-faq.html
index 181a7674..ffa7bd20 100644
--- a/htdocs/conduct-faq.html
+++ b/htdocs/conduct-faq.html
@@ -63,7 +63,7 @@ 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://creativecommons.org/licenses/by-sa/4.0/;>
 https://licensebuttons.net/l/by-sa/4.0/88x31.png;>
 This work is licensed under a
diff --git a/htdocs/conduct-report.html b/htdocs/conduct-report.html
index 139cd6c7..097309ae 100644
--- a/htdocs/conduct-report.html
+++ b/htdocs/conduct-report.html
@@ -113,7 +113,7 @@ 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://creativecommons.org/licenses/by-sa/4.0/;>
 https://licensebuttons.net/l/by-sa/4.0/88x31.png;>
 This work is licensed under a
diff --git a/htdocs/conduct-response.html b/htdocs/conduct-response.html
index d646b2e7..fb2c26f3 100644
--- a/htdocs/conduct-response.html
+++ b/htdocs/conduct-response.html
@@ -132,7 +132,7 @@ 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://creativecommons.org/licenses/by-sa/4.0/;>
 https://licensebuttons.net/l/by-sa/4.0/88x31.png;>
 This work is licensed under a
diff --git a/htdocs/conduct.html b/htdocs/conduct.html
index 2e7628af..a4cd186f 100644
--- a/htdocs/conduct.html
+++ b/htdocs/conduct.html
@@ -114,7 +114,7 @@ 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://creativecommons.org/licenses/by-sa/4.0/;>
 https://licensebuttons.net/l/by-sa/4.0/88x31.png;>
 This work is licensed under a
-- 
2.43.0

[wwwdocs] gcc-14/changes.html: Update C++ news for GCC 14

[Marek Polacek]

Pushed.  I still need to trawl all C++ commits to highlight the interesting
user-visible changes.

commit 4304a8b720b1e605a47e2da4c5a0ad21e3f05dec
Author: Marek Polacek 
Date:   Thu Nov 30 09:48:36 2023 -0500

changes.html: Update C++ news for GCC 14

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index e7779324..5a453437 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -129,12 +129,32 @@ a work-in-progress.
 
   Several C++26 features have been implemented:
 
+  https://wg21.link/P1854R4;>P1854R4, Making non-encodable
+  string literals ill-formed (https://gcc.gnu.org/PR110341;>PR110341)
+  
   https://wg21.link/P2752R3;>P2752R3, Static storage for
   braced initializers (https://gcc.gnu.org/PR110346;>PR110346)
   
+  https://wg21.link/P2361R6;>P2361R6, Unevaluated strings
+  (https://gcc.gnu.org/PR110342;>PR110342)
+  
+  https://wg21.link/P2738R1;>P2738R1, constexpr cast from
+  void*
+  (https://gcc.gnu.org/PR110344;>PR110344)
+  
+  https://wg21.link/P2741R3;>P2741R3, User-generated
+  static_assert messages
+  (https://gcc.gnu.org/PR110348;>PR110348)
+  
+  https://wg21.link/P2169R4;>P2169R4, Placeholder 
variables
+  with no name
+  (https://gcc.gnu.org/PR110349;>PR110349)
+  
+  https://wg21.link/P2864R2;>P2864R2, Removing deprecated
+  arithmetic conversion on enumerations
 
   
-  Several C++23 features have been implemented:
+  A C++23 feature has been implemented:
 
   https://wg21.link/P2280R4;>P2280R4, Using unknown
   references in constant expressions
@@ -142,6 +162,16 @@ a work-in-progress.
   
 
   
+  Several C++ Defect Reports have been resolved, e.g.:
+
+  https://wg21.link/cwg976;>DR 976,
+  Deduction for const T& conversion operators
+  https://wg21.link/cwg2406;>DR 2406,
+  [[fallthrough]] attribute and iteration statements
+  https://wg21.link/cwg2543;>DR 2543,
+  constinit and optimized dynamic initialization
+
+  
 
 
 Runtime Library (libstdc++)

Re: [wwwdocs][patch][OpenACC] gcc-14/changes.html: OpenACC - mention support for first 2.7 features

[Tobias Burnus]

On 26.11.23 09:48, Gerald Pfeifer wrote:

On Fri, 24 Nov 2023, Tobias Burnus wrote:

Comments before I commit it?

+  https://gcc.gnu.org/wiki/OpenACC
+OpenACC 2.7: The self clause was added to be used on
+  compute constructs and the default clause for data
+  constructs.
+  
+  

Where does that  come from? I'm afraid this won't validate/render
properly.


That's the disadvantage of splitting patches from the same file ... The
'' starts / should start just before the quoted line, namely as
attached. (Updated patch attach - minor changes but syntactically relevant.)

Tobias
-
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 
München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas 
Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht 
München, HRB 106955
gcc-14/changes.html: OpenACC - mention support for first 2.7 features

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 2088ee91..4ceed13d 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -90,6 +91,13 @@ a work-in-progress.
 
   
   
+  https://gcc.gnu.org/wiki/OpenACC;>OpenACC
+  
+OpenACC 2.7: The self clause was added to be used on
+  compute constructs and the default clause for data
+  constructs.
+  
+  
   For offload-device code generated via OpenMP and OpenACC, the math
   and the Fortran runtime libraries will now automatically be linked,
   when the user or compiler links them on the host side. Thus, it is no

RE: [PATCH] [gcc-wwwdocs]gcc-13/14: Mention Intel new ISA and march support

[Jiang, Haochen]

> -Original Message-
> From: Gerald Pfeifer 
> Sent: Saturday, November 25, 2023 7:29 PM
> To: Jiang, Haochen 
> Cc: gcc-patches@gcc.gnu.org; Liu, Hongtao ;
> ubiz...@gmail.com
> Subject: Re: [PATCH] [gcc-wwwdocs]gcc-13/14: Mention Intel new ISA and march
> support
> 
> On Mon, 17 Jul 2023, Haochen Jiang via Gcc-patches wrote:
> >GCC now supports the Intel CPU named Granite Rapids through
> >  -march=graniterapids.
> > +The switch enables the AMX-FP16, PREFETCHI ISA extensions.
> 
> Do I understand correclty that it enables AMX-FP16 and PREFETCHI?
> 
> How about changing this to use "and", as in
>   "The switch enables the AMX-FP16, PREFETCHI ISA extensions."
> ?
> 
> Let me know, and I can make the change.
> 

Ok for me.

Thx,
Haochen

> Gerald

Re: [wwwdocs][patch][OpenACC] gcc-14/changes.html: OpenACC - mention support for first 2.7 features

[Andreas Schwab]

On Nov 26 2023, Gerald Pfeifer wrote:

> On Fri, 24 Nov 2023, Tobias Burnus wrote:
>> Comments before I commit it?
>
> +  https://gcc.gnu.org/wiki/OpenACC;>OpenACC
> +OpenACC 2.7: The self clause was added to be used on
> +  compute constructs and the default clause for data
> +  constructs.


> +  
> +  
>
> Where does that  come from? I'm afraid this won't validate/render 
> properly.

Neither that extra , I think.

-- 
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

Re: [wwwdocs][patch][OpenACC] gcc-14/changes.html: OpenACC - mention support for first 2.7 features

[Gerald Pfeifer]

On Fri, 24 Nov 2023, Tobias Burnus wrote:
> Comments before I commit it?

+  https://gcc.gnu.org/wiki/OpenACC;>OpenACC
+OpenACC 2.7: The self clause was added to be used on
+  compute constructs and the default clause for data
+  constructs.
+  
+  

Where does that  come from? I'm afraid this won't validate/render 
properly.

Gerald

[pushed] wwwdocs: reading: Update the MicroBlaze section

[Gerald Pfeifer]

MicroBlaze is now with AMD, spelt MicroBlaze not MicroBlace, and the
docs have a new address.
---
 htdocs/readings.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/htdocs/readings.html b/htdocs/readings.html
index 2e320945..e4e68909 100644
--- a/htdocs/readings.html
+++ b/htdocs/readings.html
@@ -192,9 +192,9 @@ names.
SID includes a MeP simulator.
  
 
- MicroBlace
-   Manufacturer: Xilinx
-   https://www.xilinx.com/htmldocs/xilinx11/mb_ref_guide.pdf;>
+ MicroBlaze
+   Manufacturer: AMD
+   https://docs.xilinx.com/v/u/en-US/ug984-vivado-microblaze-ref;>
  MicroBlaze Processor Reference Guide
GDB includes a simulator for an earlier version of the processor.
  
-- 
2.42.1

[pushed] wwwdocs: gcc-13: Refer to GCC (instead of gcc)

[Gerald Pfeifer]

Refer to the overall project as GCC.

Pushed.

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

diff --git a/htdocs/gcc-13/porting_to.html b/htdocs/gcc-13/porting_to.html
index db0bf2fa..c727d66f 100644
--- a/htdocs/gcc-13/porting_to.html
+++ b/htdocs/gcc-13/porting_to.html
@@ -73,7 +73,7 @@ may change behavior or fail to compile in C++23.  For 
example:
 implicit move, whereby the compiler does two separate overload resolutions:
 one treating the operand as an rvalue, and then (if that resolution fails)
 another one treating the operand as an lvalue.  In the standard this was
-introduced in C++11 and implemented in gcc in
+introduced in C++11 and implemented in GCC in
 https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=4ce8c5dea53d80736b9c0ba6faa7430ed65ed365;>
 r251035.  In
 https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=1722e2013f05f1f1f99379dbaa0c0df356da731f;>
-- 
2.42.1

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

[Tobias Burnus]

Gerald Pfeifer wrote:

On Fri, 24 Nov 2023, Tobias Burnus wrote:

While I expect more changes, I want to cleanup my stashed changes.


Good approach!

+  The destory now optionally accepts the depend object as
+  argument.

Is "depend object" a well known technical term in that context? And is it
"the depend object" or "a depend object"?


In this context is well known; the 'destroy' clause only exists for the
'depobj' directive and the still unimplemented 'interop' directive.

In OpenMP 5.1, the syntax was:

omp_depend_t obj;
#pragma omp depobj(obj) destroy

In OpenMP draft 6.0 (TR11/T12):

#pragma omp depobj(obj) destroy(obj)

In OpenMP 5.2, both are variants valid (deprecating the 5.1 syntax).
As there is only a single depend object 'obj' per directive, even when
specified twice, I think talking about "the" makes sense.

(I opened a specification issue discuss about avoiding the duplication - 
and to clarify a couple of other issues related to 'destroy'.)


Tobias

Re: [PATCH] [gcc-wwwdocs]gcc-13/14: Mention Intel new ISA and march support

[Gerald Pfeifer]

On Mon, 17 Jul 2023, Haochen Jiang via Gcc-patches wrote:
>GCC now supports the Intel CPU named Granite Rapids through
>  -march=graniterapids.
> +The switch enables the AMX-FP16, PREFETCHI ISA extensions.

Do I understand correclty that it enables AMX-FP16 and PREFETCHI?

How about changing this to use "and", as in
  "The switch enables the AMX-FP16, PREFETCHI ISA extensions."
?

Let me know, and I can make the change.

Gerald

[pushed] wwwdocs: readings: Update OpenPOWER link

[Gerald Pfeifer]

This is the original patch and a follow-up to fix an embarrassing markup 
mistake.

Gerald


commit 17418f262b17680a07a4493631aa0743b5fe9780
Author: Gerald Pfeifer 
Date:   Fri Nov 24 09:33:26 2023 +0100

readings: Update OpenPOWER link

The original link now redirects to a very generic page; refer to the
OpenPOWER Foundation instead.

diff --git a/htdocs/readings.html b/htdocs/readings.html
index 26f2af7a..90ad35d9 100644
--- a/htdocs/readings.html
+++ b/htdocs/readings.html
@@ -269,7 +269,7 @@ names.
  
  rs6000 (powerpc, powerpcle)
   Manufacturer: IBM, Motorola
-  https://www.ibm.com/systems/power/openpower/;>Power ISA
+  https://openpowerfoundation.org>OpenPOWER Foundation
   https://openpowerfoundation.org/?resource_lib=64-bit-elf-v2-abi-specification-power-architecture;>64-Bit
 ELF V2 ABI - OpenPOWER ABI
   https://www.ibm.com/docs/en/ssw_aix_72/assembler/assembler_pdf.pdf;>AIX 
7.2 Assembler Language Reference
  

commit ed16b71d535241fab09e85991dbaf7896524c72e
Author: Gerald Pfeifer 
Date:   Sat Nov 25 10:45:23 2023 +0100

readings: Fix markup around OpenPOWER

diff --git a/htdocs/readings.html b/htdocs/readings.html
index 90ad35d9..2e320945 100644
--- a/htdocs/readings.html
+++ b/htdocs/readings.html
@@ -269,7 +269,7 @@ names.
  
  rs6000 (powerpc, powerpcle)
   Manufacturer: IBM, Motorola
-  https://openpowerfoundation.org>OpenPOWER Foundation
+  https://openpowerfoundation.org;>OpenPOWER Foundation
   https://openpowerfoundation.org/?resource_lib=64-bit-elf-v2-abi-specification-power-architecture;>64-Bit
 ELF V2 ABI - OpenPOWER ABI
   https://www.ibm.com/docs/en/ssw_aix_72/assembler/assembler_pdf.pdf;>AIX 
7.2 Assembler Language Reference
  

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

[Gerald Pfeifer]

On Fri, 24 Nov 2023, Tobias Burnus wrote:
> While I expect more changes, I want to cleanup my stashed changes.

Good approach!

+  The destory now optionally accepts the depend object as
+  argument.

Is "depend object" a well known technical term in that context? And is it 
"the depend object" or "a depend object"?

Gerald

Re: [wwwdocs][patch][GCN] gcc-14/changes.html: GCN - Mention improvements due to VGPR register use

[Gerald Pfeifer]

On Fri, 24 Nov 2023, Tobias Burnus wrote:
> As in a set of benchmarks, an geometric-mean improvement of 9% (noise to 
> 25%) was found, I think we should mention this improvement proudly.

Definitely!

> Comments?

The ", hence," broke my reading flow; maybe simply omit it? Either way, 
okay.

Gerald

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

[Jakub Jelinek]

On Fri, Nov 24, 2023 at 05:26:44PM +0100, Tobias Burnus wrote:
> @@ -65,8 +72,11 @@
>was extended. Additionally, the spec change has been implemented for
>default implicit mapping of C/C++ pointers pointing to unmapped 
> storage.
> +  The destory now optionally accepts the depend object as

s/destory/destroy/

Otherwise LGTM.

Jakub

[wwwdocs][patch][OpenMP] gcc-14/changes.html + projects/gomp/: OpenMP update

[Tobias Burnus]

While I expect more changes, I want to cleanup my stashed changes.

Current version: https://gcc.gnu.org/gcc-14/changes.html#openmp

Comments?

Tobias

PS: stack variable support in C++ for 'allocate' is pending review;
I also expect a Fortran parser update for 'indirect'. Several more
features are also pending review.
-
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 
München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas 
Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht 
München, HRB 106955
gcc-14/changes.html + projects/gomp/: OpenMP update

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 455798d1..c9d5f08a 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -54,8 +55,14 @@
   requirement is now fulfilled by both AMD GCN and nvptx devices.
 
+OpenMP 5.0: The allocate/ directive is now
+  supported for stack variables in C and Fortran, including the OpenMP 5.1
+  align modifier.
 
   OpenMP 5.1: Support was added for collapsing imperfectly nested loops and
   using present as map-type modifier and in
-  defaultmap.
+  defaultmap. The indirect clause is now supported
+  for C and C++.  The performance of copying strided data from or to nvptx
+  devices using the OpenMP 5.1 routine omp_target_memcpy_rect
+  has been improved.
 
 
@@ -65,8 +72,11 @@
   was extended. Additionally, the spec change has been implemented for
   default implicit mapping of C/C++ pointers pointing to unmapped storage.
+  The destory now optionally accepts the depend object as
+  argument.
 
 
-  OpenMP 6.0 preview (TR11): The decl attribute is now
-  supported in C++ 11 attributes.
+  OpenMP 6.0 preview (TR11/TR12): The decl attribute is now
+  supported in C++ 11 and the directive, sequence
+  and decl attributes are now supported in C 23.
 
 
diff --git a/htdocs/projects/gomp/index.html b/htdocs/projects/gomp/index.html
index bc472747..4795ce89 100644
--- a/htdocs/projects/gomp/index.html
+++ b/htdocs/projects/gomp/index.html
@@ -822,5 +822,5 @@ than listed, depending on resolved corner cases and optimizations.
   
 Deprecation of no-argument destroy clause on depobj
-No
+GCC14
 
   

[wwwdocs][patch][OpenACC] gcc-14/changes.html: OpenACC - mention support for first 2.7 features

[Tobias Burnus]

Comments before I commit it?

Current version: https://gcc.gnu.org/gcc-14/changes.html#general

Tobias
-
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 
München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas 
Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht 
München, HRB 106955
gcc-14/changes.html: OpenACC - mention support for first 2.7 features

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 455798d1..c9d5f08a 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -81,4 +91,10 @@ a work-in-progress.
   
   
+  https://gcc.gnu.org/wiki/OpenACC;>OpenACC
+OpenACC 2.7: The self clause was added to be used on
+  compute constructs and the default clause for data
+  constructs.
+  
+  
   For offload-device code generated via OpenMP and OpenACC, the math
   and the Fortran runtime libraries will now automatically be linked,

[wwwdocs][patch][GCN] gcc-14/changes.html: GCN - Mention improvements due to VGPR register use

[Tobias Burnus]

As in a set of benchmarks, an geometric-mean improvement of 9% (noise to 25%)
was found, I think we should mention this improvement proudly.
(Kudos goes to two Andrews - Jenner and Stubbs!)

Current version: https://gcc.gnu.org/gcc-14/changes.html#amdgcn

Comments?

Tobias
-
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 
München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas 
Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht 
München, HRB 106955
gcc-14/changes.html: GCN - Mention improvements due to VGPR register use

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 455798d1..1fa74f9a 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -191,6 +211,8 @@
 AMD Radeon (GCN)
 
 
+  Improved register usage and, hence, performance on CDNA Instinct MI100
+and MI200 series devices.
   The default device architecture is now gfx900 (Vega).
   
 Fiji (gfx803) device support is now deprecated and will be removed from

Re: [pushed] wwwdocs: *: Remove unused buildstat pages

[Gerald Pfeifer]

On Mon, 20 Nov 2023, Thomas Schwinge wrote:
>> 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.
> ACK; I had recently run into such an empty page, and wanted to suggest
> the same.
> 
> We still need to update the docs some more.  Do we just remove all
> references (and related text), and/or refer to the gcc-testresults
> mailing list?

The libstdc++ docs refer to gcc-results and I'll see to add this to the 
web pages where applicable.

> In wwwdocs:
> 
> htdocs/branching.html:Add buildstat.html and update the 
> toplevel
> htdocs/branching.html:buildstat.html accordingly.
> 
> htdocs/faq.html:Reports of successful builds
> htdocs/faq.html-for several versions of GCC are also available at the web 
> site.
> 
> htdocs/releasing.html-For a new major release, ensure that the build 
> status page is present
> htdocs/releasing.html:and add a link from the main 
> buildstat.html page.

I have taken care of all these and will look into gcc/doc/install.texi in 
the coming days.

Thanks for bringing this up!

Gerald

[pushed] wwwdocs: conduct: Use licensebuttons.net

[Gerald Pfeifer]

i.creativecommons.org now has a permanent redirect for the images
we use to licensebuttons.net, so follow that.

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 06f579b9..181a7674 100644
--- a/htdocs/conduct-faq.html
+++ b/htdocs/conduct-faq.html
@@ -64,7 +64,8 @@ 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;>
+https://licensebuttons.net/l/by-sa/4.0/88x31.png;>
 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 1913185b..139cd6c7 100644
--- a/htdocs/conduct-report.html
+++ b/htdocs/conduct-report.html
@@ -114,7 +114,8 @@ 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;>
+https://licensebuttons.net/l/by-sa/4.0/88x31.png;>
 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-response.html b/htdocs/conduct-response.html
index 42509828..d646b2e7 100644
--- a/htdocs/conduct-response.html
+++ b/htdocs/conduct-response.html
@@ -133,7 +133,8 @@ 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;>
+https://licensebuttons.net/l/by-sa/4.0/88x31.png;>
 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.html b/htdocs/conduct.html
index e04188de..2e7628af 100644
--- a/htdocs/conduct.html
+++ b/htdocs/conduct.html
@@ -115,7 +115,8 @@ 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;>
+https://licensebuttons.net/l/by-sa/4.0/88x31.png;>
 This work is licensed under a
 https://creativecommons.org/licenses/by-sa/4.0/;>
 Creative Commons Attribution-ShareAlike 4.0 International License.
-- 
2.42.1

[pushed] wwwdocs: faq: Refer to gcc-testresults instead of buildstat.html

[Gerald Pfeifer]

This is the last obsolete reference to buildstat.html shared by Thomas 
and per my own `grep -r`.

Pushed.

Gerald

---
 htdocs/faq.html | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/htdocs/faq.html b/htdocs/faq.html
index 203661dc..5c713a70 100644
--- a/htdocs/faq.html
+++ b/htdocs/faq.html
@@ -99,8 +99,9 @@ about known problems with installing or using GCC on 
particular platforms.
 These are included in the sources for a release in INSTALL/specific.html,
 and the https://gcc.gnu.org/install/specific.html;>latest version
 is always available at the GCC web site.
-Reports of successful builds
-for several versions of GCC are also available at the web site.
+There you also find
+https://gcc.gnu.org/pipermail/gcc-testresults/;>reports around
+successful builds.
 
 
 Installation
-- 
2.42.1

[pushed] wwwdocs: branching: No longer refer to buildstat.html

[Gerald Pfeifer]

Thomas spotted this (among others) not being necessary any longer and 
kindly reported it.

Pushed.
---
 htdocs/branching.html | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/htdocs/branching.html b/htdocs/branching.html
index 0d48dce1..23ff92e8 100644
--- a/htdocs/branching.html
+++ b/htdocs/branching.html
@@ -52,9 +52,6 @@ populate it with initial copies of changes.html 
and
 based on the previous release branch to the directory corresponding to
 the newly created release branch.

-Add buildstat.html and update the toplevel
-buildstat.html accordingly.
-
 Update the toplevel index.html page to show the new active
 release branch, the current release series, and active development
 (mainline).  Update the version and development stage for mainline.
-- 
2.42.1

[pushed] wwwdocs: releasing: No longer refer to buildstat.html

[Gerald Pfeifer]

That's the counterpart to the branching.html change I just made, also 
reported by Thomas.

Pushed.

Gerald
---
 htdocs/releasing.html | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/htdocs/releasing.html b/htdocs/releasing.html
index 1cd56f72..c7365e64 100644
--- a/htdocs/releasing.html
+++ b/htdocs/releasing.html
@@ -85,9 +85,6 @@ web pages.
 Update the version numbers of the current and future releases on
 the main web page, and add a proper news item there as well.
 
-For a new major release, ensure that the build status page is present
-and add a link from the main buildstat.html page.
-
 Generate online documentation for the new release with
 update_web_docs_git.  The appropriate command to run (as gccadmin)
 to generate the documentation would be scripts/update_web_docs_git
-- 
2.42.1

Re: [pushed] wwwdocs: *: Remove unused buildstat pages

[Jonathan Wakely]

On Mon, 20 Nov 2023 at 08:42, Thomas Schwinge  wrote:
>
> Hi!
>
> On 2023-10-15T23:42:39+0200, Gerald Pfeifer  wrote:
> > [ 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.
>
> ACK; I had recently run into such an empty page, and wanted to suggest
> the same.
>
> We still need to update the docs some more.  Do we just remove all
> references (and related text), and/or refer to the gcc-testresults
> mailing list?
>
> In wwwdocs:
>
> htdocs/branching.html:Add buildstat.html and update the 
> toplevel
> htdocs/branching.html:buildstat.html accordingly.
>
> htdocs/faq.html:Reports of successful builds
> htdocs/faq.html-for several versions of GCC are also available at the web 
> site.
>
> htdocs/releasing.html-For a new major release, ensure that the build 
> status page is present
> htdocs/releasing.html:and add a link from the main 
> buildstat.html page.
>
> In GCC:
>
> gcc/doc/install.texi-Lists of successful builds for released versions of 
> GCC are
> gcc/doc/install.texi:available at 
> @uref{https://gcc.gnu.org/buildstat.html}.
> gcc/doc/install.texi-These lists are updated as new information becomes 
> available.
>
> gcc/doc/install.texi-Some of these archived results are linked from the 
> build status lists
> gcc/doc/install.texi:at @uref{https://gcc.gnu.org/buildstat.html}, 
> although not everyone who
> gcc/doc/install.texi-reports a successful build runs the testsuites and 
> submits the results.
>
> gcc/doc/install.texi-If you are bootstrapping a released version of GCC 
> then please
> gcc/doc/install.texi-quickly review the build status page for your 
> release, available from
> gcc/doc/install.texi:@uref{https://gcc.gnu.org/buildstat.html}.
>
> libstdc++-v3/doc/xml/faq.xml-the rapid development and near-legendary
> libstdc++-v3/doc/xml/faq.xml: xmlns:xlink="http://www.w3.org/1999/xlink; 
> xlink:href="https://gcc.gnu.org/buildstat.html;>portability
> libstdc++-v3/doc/xml/faq.xml-that are the hallmarks of an open-source 
> project are applied to libstdc++.
>
> libstdc++-v3/doc/xml/manual/test.xml-   Archives of test results for 
> various versions and platforms are
> libstdc++-v3/doc/xml/manual/test.xml:   available on the GCC website 
> in the http://www.w3.org/1999/xlink; 
> xlink:href="http://gcc.gnu.org/gcc-4.3/buildstat.html;>build
> libstdc++-v3/doc/xml/manual/test.xml-   status section of each 
> individual release, and are also
> libstdc++-v3/doc/xml/manual/test.xml-   archived on a daily basis on 
> the http://www.w3.org/1999/xlink; 
> xlink:href="http://gcc.gnu.org/ml/gcc-testresults/current;>gcc-testresults


Good point. I'll push the attached patch to the docs.
commit fd7a339512b60545700124b21700fb86a6527f76
Author: Jonathan Wakely 
Date:   Mon Nov 20 12:41:30 2023

libstdc++: Remove outdated references to buildstat.html

The buildstat.html pages have not existed since gcc-8 so remove
referencs to them in the libstdc++ manual.

libstdc++-v3/ChangeLog:

* doc/html/*: Regenerate.
* doc/xml/faq.xml: Remove reference to buildstat.html pages.
* doc/xml/manual/test.xml: Likewise

diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-v3/doc/xml/faq.xml
index da41199584e..79edb02bec4 100644
--- a/libstdc++-v3/doc/xml/faq.xml
+++ b/libstdc++-v3/doc/xml/faq.xml
@@ -64,9 +64,8 @@
 (gcc, g++, etc) is widely
 considered to be one of the leading compilers in the world.  Its
 development is overseen by the
-http://www.w3.org/1999/xlink; 
xlink:href="https://gcc.gnu.org/;>GCC team.  All of
-the rapid development and near-legendary
-http://www.w3.org/1999/xlink; 
xlink:href="https://gcc.gnu.org/buildstat.html;>portability
+http://www.w3.org/1999/xlink; 
xlink:href="https://gcc.gnu.org/;>GCC team.
+All of the rapid development and near-legendary portability
 that are the hallmarks of an open-source project are applied to libstdc++.
 
 
diff --git a/libstdc++-v3/doc/xml/manual/test.xml 
b/libstdc++-v3/doc/xml/manual/test.xml
index 936f97417af..f2c709bc6bf 100644
--- a/libstdc++-v3/doc/xml/manual/test.xml
+++ b/libstdc++-v3/doc/xml/manual/test.xml
@@ -266,10 +266,8 @@ cat 27_io/objects/char/3_xin.in | a.out
 
  
Archives of test results for various versions and platforms are
-   available on the GCC website in the http://www.w3.org/1999/xlink; 
xlink:href="http://gcc.gnu.org/gcc-4.3/buildstat.

[wwwdocs] Add new libstdc++ features

[Jonathan Wakely]

Pushed to wwwdocs.

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

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index e5d3970c..7278f753 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -138,12 +138,16 @@ a work-in-progress.
 Formatters for std::thread::id and
   std::stacktrace.
 
+Smart pointer adaptors, std::out_ptr and
+  std::inout_ptr.
+
 Some range adaptors now support move-only types.
 
   
   Experimental support for C++26, including:
 
 Native handles for filebuf, fstream, 
etc.
+Functions for saturation arithmetic on integers.
 std::to_string now uses std::format.
 Enhanced formatting of pointers with std::format.
 Testable result types for charconv functions.
@@ -160,6 +164,9 @@ a work-in-progress.
   Using the std::setfill manipulator with
 std::istream is deprecated.
   
+  Added missing functions for float and
+long double to cmath.
+  
 
 
 
-- 
2.42.0

Re: [pushed] wwwdocs: *: Remove unused buildstat pages

[Thomas Schwinge]

Hi!

On 2023-10-15T23:42:39+0200, Gerald Pfeifer  wrote:
> [ 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.

ACK; I had recently run into such an empty page, and wanted to suggest
the same.

We still need to update the docs some more.  Do we just remove all
references (and related text), and/or refer to the gcc-testresults
mailing list?

In wwwdocs:

htdocs/branching.html:Add buildstat.html and update the 
toplevel
htdocs/branching.html:buildstat.html accordingly.

htdocs/faq.html:Reports of successful builds
htdocs/faq.html-for several versions of GCC are also available at the web 
site.

htdocs/releasing.html-For a new major release, ensure that the build 
status page is present
htdocs/releasing.html:and add a link from the main 
buildstat.html page.

In GCC:

gcc/doc/install.texi-Lists of successful builds for released versions of 
GCC are
gcc/doc/install.texi:available at @uref{https://gcc.gnu.org/buildstat.html}.
gcc/doc/install.texi-These lists are updated as new information becomes 
available.

gcc/doc/install.texi-Some of these archived results are linked from the 
build status lists
gcc/doc/install.texi:at @uref{https://gcc.gnu.org/buildstat.html}, although 
not everyone who
gcc/doc/install.texi-reports a successful build runs the testsuites and 
submits the results.

gcc/doc/install.texi-If you are bootstrapping a released version of GCC 
then please
gcc/doc/install.texi-quickly review the build status page for your release, 
available from
gcc/doc/install.texi:@uref{https://gcc.gnu.org/buildstat.html}.

libstdc++-v3/doc/xml/faq.xml-the rapid development and near-legendary
libstdc++-v3/doc/xml/faq.xml:http://www.w3.org/1999/xlink; 
xlink:href="https://gcc.gnu.org/buildstat.html;>portability
libstdc++-v3/doc/xml/faq.xml-that are the hallmarks of an open-source 
project are applied to libstdc++.

libstdc++-v3/doc/xml/manual/test.xml-   Archives of test results for 
various versions and platforms are
libstdc++-v3/doc/xml/manual/test.xml:   available on the GCC website in 
the http://www.w3.org/1999/xlink; 
xlink:href="http://gcc.gnu.org/gcc-4.3/buildstat.html;>build
libstdc++-v3/doc/xml/manual/test.xml-   status section of each 
individual release, and are also
libstdc++-v3/doc/xml/manual/test.xml-   archived on a daily basis on 
the http://www.w3.org/1999/xlink; 
xlink:href="http://gcc.gnu.org/ml/gcc-testresults/current;>gcc-testresults


Grüße
 Thomas


>  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

[wwwdocs][committed] projects/gomp: Update for TR12, update impl. status

[Tobias Burnus]

A new OpenMP 6.0 preview, Technical Report (TR) 12 has been released in time 
for Supercomputing 2023 (SC23),
cf.https://www.openmp.org/specifications/

This commit links to the new spec (see bottom of change), it also updates the
implementation status of some items for 'allocate', 'indirect' and C++23/C23 
attributes,
and, mainly, updates it for new features added between TR11 and TR12.

Committed - looks like:
  https://gcc.gnu.org/projects/gomp/
esp, see "TR 12" and "OpenMP Releases and Status"

Tobias

PS: The libgomp.texi update is at 
https://gcc.gnu.org/onlinedocs/libgomp/OpenMP-Implementation-Status.html
-> TR12 (I need to fix the typo 'c(a)lause' there) and some update for
https://gcc.gnu.org/gcc-14/changes.html is also eventually required.
But as more features keep getting added, there is no rush.
-
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 
München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas 
Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht 
München, HRB 106955
commit ad756d3cfed3007d8c07c7f22facf24b202f1160
Author: Tobias Burnus 
Date:   Mon Nov 13 10:23:25 2023 +0100

projects/gomp: Update for TR12, update impl. status

This adds a link to the new TR12 (second OpenMP 6.0 preview); updates
the status + TR12 to-do list form libgomp.texi and adds a couple of
missing ''.
---
 htdocs/projects/gomp/index.html | 248 +---
 1 file changed, 205 insertions(+), 43 deletions(-)

diff --git a/htdocs/projects/gomp/index.html b/htdocs/projects/gomp/index.html
index 7f0b97c3..bc472747 100644
--- a/htdocs/projects/gomp/index.html
+++ b/htdocs/projects/gomp/index.html
@@ -29,7 +29,7 @@ OpenMP and OpenACC are supported with GCC's C, C++ and Fortran compilers.
   3.1 · 4.0 ·
   4.5 · 5.0 ·
   5.1 · 5.2 ·
-  TR 11
+  TR 12
   OpenMP Releases and Status
 
 
@@ -480,7 +480,7 @@ than listed, depending on resolved corner cases and optimizations.
   
 allocate directive
 GCC14
-Only C, only stack variables
+Only C and Fortran, only stack variables
   
   
 Discontiguous array section with target update construct
@@ -555,7 +555,7 @@ than listed, depending on resolved corner cases and optimizations.
   
 align clause in allocate directive
 GCC14
-Only C (and only stack variables)
+Only C and Fortran (and only stack variables)
   
   
 align modifier in allocate clause
@@ -708,14 +708,14 @@ than listed, depending on resolved corner cases and optimizations.
 
   
   
-iterators in target update motion clauses and map clauses
+.terators in target update motion clauses and map clauses
 No
 
   
   
-indirect calls to the device version of a procedure or function in target regions
-No
-
+Indirect calls to the device version of a procedure or function in target regions
+GCC14
+Only C and C++
   
   
 interop directive
@@ -745,7 +745,7 @@ than listed, depending on resolved corner cases and optimizations.
   
   
 For Fortran, diagnose placing declarative before/between USE,
-  IMPORT, and IMPLICIT as invalid
+  IMPORT, and IMPLICIT as invalid
 No
 
   
@@ -756,8 +756,8 @@ than listed, depending on resolved corner cases and optimizations.
   
   
 indirect clause in declare target
-No
-
+GCC14
+Only C and C++
   
   
 device_type(nohost)/device_type(host) for variables
@@ -964,6 +964,12 @@ than listed, depending on resolved corner cases and optimizations.
 No
 
   
+  
+Invoke virtual member functions of C++ objects created on the host
+  device on other devices
+No
+
+  
 
 
 
@@ -976,9 +982,9 @@ code, the omx sentinel is warned for with -Wsurprising
 (enabled by -Wall). Unknown clauses are always rejected with an
 error.
 
-OpenMP Technical Report 11
+OpenMP Technical Report 12
 
-Technical Report (TR) 11 is the first preview for OpenMP 6.0.
+Technical Report (TR) 12 is the second preview for OpenMP 6.0.
 
 
 
@@ -995,18 +1001,90 @@ error.
 Backward compatibility
   
   
-The decl attribute was added to the C++ attribute syntax
-GCC14
-
+Full support for C 23 was added
+GCC9
+/ GCC14
+Increasing coverage (since GCC 9 -std=c2x,
+since GCC 14 -std=c23)
   
   
-_ALL suffix to the device-scope environment variables
+Full support for C++ 23 was added
+GCC11
+/ GCC14
+https://gcc.gnu.org/projects/cxx-status.html;>C++ Implementation Status;
+increasing coverage (since GCC 11 -std=c++2b,
+since GCC 14 -std=c++23)
+  
+  
+_ALL suffix to the device-scope environment variables
 GCC13
 Host device number wrongly accepted
   
+  
+num_threads now accepts a list
+No
+
+  
+  
+Supporting increments with abstract names in OMP_PLACES
+No
+
+  
+  
+Extension of OMP_DEFAULT_DEVICE and new
+  OMP_AVAILABLE_DEVICES environment vars
+   

[committed][wwwdocs] Uncomment link to "Porting to GCC 14"

[Jonathan Wakely]

Pushed to wwwdocs.

-- >8 --

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

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 5611fc4f..e5d3970c 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -17,11 +17,9 @@
 
 This page is a "brief" summary of some of the huge number of improvements
 in GCC 14.
-
 
 
 Note: GCC 14 has not been released yet, so this document is
-- 
2.41.0

[committed][wwwdocs] Add "Porting to GCC 14"

[Jonathan Wakely]

Pushed to wwwdocs.

-- >8 --

---
 htdocs/gcc-14/porting_to.html | 50 +++
 1 file changed, 50 insertions(+)
 create mode 100644 htdocs/gcc-14/porting_to.html

diff --git a/htdocs/gcc-14/porting_to.html b/htdocs/gcc-14/porting_to.html
new file mode 100644
index ..dea9ac80
--- /dev/null
+++ b/htdocs/gcc-14/porting_to.html
@@ -0,0 +1,50 @@
+
+
+
+
+
+Porting to GCC 14
+https://gcc.gnu.org/gcc.css;>
+
+
+
+Porting to GCC 14
+
+
+The GCC 14 release series differs from previous GCC releases in
+a number of ways. Some of these are a result
+of bug fixing, and some old behaviors have been intentionally changed
+to support new standards, or relaxed in standards-conforming ways to
+facilitate compilation or run-time performance.
+
+
+
+Some of these changes are user visible and can cause grief when
+porting to GCC 14. This document is an effort to identify common issues
+and provide solutions. Let us know if you have suggestions for improvements!
+
+
+C++ language issues
+
+Header dependency changes
+Some C++ Standard Library headers have been changed to no longer include
+other headers that were being used internally by the library.
+As such, C++ programs that used standard library components without
+including the right headers will no longer compile.
+
+
+The following headers are used less widely in libstdc++ and may need to
+be included explicitly when compiling with GCC 14:
+
+
+ algorithm
+  (for std::copy_n, std::lower_bound,
+  std::remove, std::reverse,
+  std::sort etc.)
+
+
+
+
+
+
+
-- 
2.41.0

Re: [wwwdocs] Get newlib via git in simtest-howto.html

[Richard Biener]

On Fri, Oct 27, 2023 at 6:39 PM Roger Sayle  wrote:
>
>
> A minor tweak to the documentation, to use git rather than cvs to obtain
> the latest version of newlib.  Ok for mainline?

OK

>
> 2023-10-27  Roger Sayle  
>
> * htdocs/simtest-howto.html: Use git to obtain newlib.
>
> Cheers,
> Roger
> --
>

[wwwdocs] Get newlib via git in simtest-howto.html

[Roger Sayle]

A minor tweak to the documentation, to use git rather than cvs to obtain
the latest version of newlib.  Ok for mainline?


2023-10-27  Roger Sayle  

* htdocs/simtest-howto.html: Use git to obtain newlib.

Cheers,
Roger
--

diff --git a/htdocs/simtest-howto.html b/htdocs/simtest-howto.html
index 2e54476b..d9c027fd 100644
--- a/htdocs/simtest-howto.html
+++ b/htdocs/simtest-howto.html
@@ -59,9 +59,7 @@ contrib/gcc_update --touch
 
 
 cd ${TOP}
-cvs -d :pserver:anon...@sourceware.org:/cvs/src login
-# You will be prompted for a password; reply with "anoncvs".
-cvs -d :pserver:anon...@sourceware.org:/cvs/src co newlib
+git clone https://sourceware.org/git/newlib-cygwin.git newlib
 
 
 Check out the sim and binutils tree:

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

[Andrew Stubbs]

On 22/10/2023 13:24, Gerald Pfeifer wrote:

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?


Thank you for your suggestions; I have committed the attached.

Andrewgcc-14: mark amdgcn fiji deprecated


diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index c817dde4..a20499e9 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -178,6 +178,21 @@ a work-in-progress.
 
 
 
+AMD Radeon (GCN)
+
+
+  The default device architecture is now gfx900 (Vega).
+  
+Fiji (gfx803) device support is now deprecated and will be removed from
+a future release.  The default compiler configuration no longer uses Fiji
+as the default device, and no longer includes the Fiji libraries.  Both can
+be restored by configuring with
+https://gcc.gnu.org/install/specific.html#amdgcn-x-amdhsa;>
+  --with-arch=fiji
+.
+  
+
+
 
 
 

RE: [PATCH] [gcc-wwwdocs]gcc-13/14: Mention Intel new ISA and march support

[Jiang, Haochen]

> -Original Message-
> From: Jiang, Haochen 
> Sent: Friday, October 27, 2023 10:52 AM
> To: Jiang, Haochen ; gcc-patches@gcc.gnu.org
> Cc: Liu, Hongtao ; ubiz...@gmail.com; Gerald Pfeifer
> 
> Subject: RE: [PATCH] [gcc-wwwdocs]gcc-13/14: Mention Intel new ISA and
> march support
> 
> > -Original Message-
> > From: Gcc-patches  > bounces+haochen.jiang=intel@gcc.gnu.org> On Behalf Of Haochen
> > bounces+Jiang
> > via Gcc-patches
> > Sent: Monday, July 17, 2023 11:34 AM
> > To: gcc-patches@gcc.gnu.org
> > Cc: Liu, Hongtao ; ubiz...@gmail.com
> > Subject: [PATCH] [gcc-wwwdocs]gcc-13/14: Mention Intel new ISA and
> > march support
> >
> > Hi all,
> >
> > This patch adds documentation to wwwdocs to mention the recent
> > introduction of Intel new ISA and march.
> >
> > Ok for trunk?
> 
> I will commit the patch next Monday if there is no objection.

Sorry for the disturb since I find the wrong mail to reply because they
are too similar.

> 
> Thx,
> Haochen
> 
> >
> > BRs,
> > Haochen
> >
> > ---
> >  htdocs/gcc-13/changes.html |  4 
> >  htdocs/gcc-14/changes.html | 34
> > +-
> >  2 files changed, 37 insertions(+), 1 deletion(-)
> >
> > diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
> > index 39414e18..68e8c5cc 100644
> > --- a/htdocs/gcc-13/changes.html
> > +++ b/htdocs/gcc-13/changes.html
> > @@ -593,6 +593,10 @@ You may also want to check out our
> >
> >GCC now supports the Intel CPU named Granite Rapids through
> >  -march=graniterapids.
> > +The switch enables the AMX-FP16, PREFETCHI ISA extensions.
> > +  
> > +  GCC now supports the Intel CPU named Granite Rapids D through
> > +-march=graniterapids-d.
> >  The switch enables the AMX-FP16, PREFETCHI and AMX-COMPLEX ISA
> > extensions.
> >
> >GCC now supports AMD CPUs based on the znver4 core
> > diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
> > index
> > 3f797642..dad1ba53 100644
> > --- a/htdocs/gcc-14/changes.html
> > +++ b/htdocs/gcc-14/changes.html
> > @@ -108,7 +108,39 @@ a work-in-progress.
> >
> >  
> >
> > -
> > +IA-32/x86-64
> > +
> > +  New ISA extension support for Intel AVX-VNNI-INT16 was added.
> > +  AVX-VNNI-INT16 intrinsics are available via the -
> > mavxvnniint16
> > +  compiler switch.
> > +  
> > +  New ISA extension support for Intel SHA512 was added.
> > +  SHA512 intrinsics are available via the -msha512
> > +  compiler switch.
> > +  
> > +  New ISA extension support for Intel SM3 was added.
> > +  SM3 intrinsics are available via the -msm3
> > +  compiler switch.
> > +  
> > +  New ISA extension support for Intel SM4 was added.
> > +  SM4 intrinsics are available via the -msm4
> > +  compiler switch.
> > +  
> > +  GCC now supports the Intel CPU named Arrow Lake through
> > +-march=arrowlake.
> > +Based on Alder Lake, the switch further enables the AVX-IFMA,
> > +AVX-VNNI-INT8, AVX-NE-CONVERT and CMPccXADD ISA extensions.
> > +  
> > +  GCC now supports the Intel CPU named Arrow Lake S through
> > +-march=arrowlake-s.
> > +Based on Arrow Lake, the switch further enables the
> > + AVX-VNNI-INT16,
> > SHA512,
> > +SM3 and SM4 ISA extensions.
> > +  
> > +  GCC now supports the Intel CPU named Lunar Lake through
> > +-march=lunarlake.
> > +Lunar Lake is based on Arrow Lake S.
> > +  
> > +
> >
> >  
> >
> > --
> > 2.31.1

RE: [PATCH] [gcc-wwwdocs]gcc-13/14: Mention Intel new ISA and march support

[Jiang, Haochen]

> -Original Message-
> From: Gcc-patches  bounces+haochen.jiang=intel@gcc.gnu.org> On Behalf Of Haochen Jiang
> via Gcc-patches
> Sent: Monday, July 17, 2023 11:34 AM
> To: gcc-patches@gcc.gnu.org
> Cc: Liu, Hongtao ; ubiz...@gmail.com
> Subject: [PATCH] [gcc-wwwdocs]gcc-13/14: Mention Intel new ISA and march
> support
> 
> Hi all,
> 
> This patch adds documentation to wwwdocs to mention the recent
> introduction of Intel new ISA and march.
> 
> Ok for trunk?

I will commit the patch next Monday if there is no objection.

Thx,
Haochen

> 
> BRs,
> Haochen
> 
> ---
>  htdocs/gcc-13/changes.html |  4 
>  htdocs/gcc-14/changes.html | 34
> +-
>  2 files changed, 37 insertions(+), 1 deletion(-)
> 
> diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index
> 39414e18..68e8c5cc 100644
> --- a/htdocs/gcc-13/changes.html
> +++ b/htdocs/gcc-13/changes.html
> @@ -593,6 +593,10 @@ You may also want to check out our
>
>GCC now supports the Intel CPU named Granite Rapids through
>  -march=graniterapids.
> +The switch enables the AMX-FP16, PREFETCHI ISA extensions.
> +  
> +  GCC now supports the Intel CPU named Granite Rapids D through
> +-march=graniterapids-d.
>  The switch enables the AMX-FP16, PREFETCHI and AMX-COMPLEX ISA
> extensions.
>
>GCC now supports AMD CPUs based on the znver4 core
> diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html index
> 3f797642..dad1ba53 100644
> --- a/htdocs/gcc-14/changes.html
> +++ b/htdocs/gcc-14/changes.html
> @@ -108,7 +108,39 @@ a work-in-progress.
> 
>  
> 
> -
> +IA-32/x86-64
> +
> +  New ISA extension support for Intel AVX-VNNI-INT16 was added.
> +  AVX-VNNI-INT16 intrinsics are available via the -
> mavxvnniint16
> +  compiler switch.
> +  
> +  New ISA extension support for Intel SHA512 was added.
> +  SHA512 intrinsics are available via the -msha512
> +  compiler switch.
> +  
> +  New ISA extension support for Intel SM3 was added.
> +  SM3 intrinsics are available via the -msm3
> +  compiler switch.
> +  
> +  New ISA extension support for Intel SM4 was added.
> +  SM4 intrinsics are available via the -msm4
> +  compiler switch.
> +  
> +  GCC now supports the Intel CPU named Arrow Lake through
> +-march=arrowlake.
> +Based on Alder Lake, the switch further enables the AVX-IFMA,
> +AVX-VNNI-INT8, AVX-NE-CONVERT and CMPccXADD ISA extensions.
> +  
> +  GCC now supports the Intel CPU named Arrow Lake S through
> +-march=arrowlake-s.
> +Based on Arrow Lake, the switch further enables the AVX-VNNI-INT16,
> SHA512,
> +SM3 and SM4 ISA extensions.
> +  
> +  GCC now supports the Intel CPU named Lunar Lake through
> +-march=lunarlake.
> +Lunar Lake is based on Arrow Lake S.
> +  
> +
> 
>  
> 
> --
> 2.31.1

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] wwwdocs: gcc-14: mark amdgcn fiji deprecated

[Tobias Burnus]

On 20.10.23 14:58, Andrew Stubbs wrote:

Fair enough, how's this version? (I like the comma, even if it is
optional.)


LGTM – for what it is worth.

Thanks!

Tobias

-
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 
München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas 
Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht 
München, HRB 106955

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

[Andrew Stubbs]

On 19/10/2023 11:07, Tobias Burnus wrote:

On 19.10.23 11:49, Andrew Stubbs wrote:

OK to commit?


(I think as maintainer you don't need approval - but of course comments
by others can be helpful; I hope mine are. Additionally, Gerald (CCed)
helps with keeping the webpages in good shape (thanks!).)



gcc-14: mark amdgcn fiji deprecated
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index c817dde4..91ab8132 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -178,6 +178,16 @@ a work-in-progress.

  

+AMD Radeon (GCN)
+
+
+  The Fiji device support is now deprecated and will be removed 
from a
+  future release.  The default compiler configuration no longer 
uses Fiji
+  as the default device, and no longer includes the Fiji 
libraries.  Both
+  can be restored by configuring with 
--with-arch=fiji.
+  The default device architecture is now gfx900 
(Vega).

+


Can you add ... around the "--with-arch=fiji"? Linking to

https://gcc.gnu.org/install/specific.html#amdgcn-x-amdhsa

I think that page is helpful (once the cron job has updated that page).

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.)

Andrewgcc-14: mark amdgcn fiji deprecated


diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index c817dde4..23694310 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -178,6 +178,21 @@ a work-in-progress.
 
 
 
+AMD Radeon (GCN)
+
+
+  
+The Fiji (gfx803) device support is now deprecated and will be removed from
+a future release.  The default compiler configuration no longer uses Fiji
+as the default device, and no longer includes the Fiji libraries.  Both can
+be restored by configuring with
+https://gcc.gnu.org/install/specific.html#amdgcn-x-amdhsa;>
+  --with-arch=fiji
+.
+  
+  The default device architecture is now gfx900 (Vega).
+
+
 
 
 

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

[Tobias Burnus]

On 19.10.23 11:49, Andrew Stubbs wrote:

OK to commit?


(I think as maintainer you don't need approval - but of course comments
by others can be helpful; I hope mine are. Additionally, Gerald (CCed)
helps with keeping the webpages in good shape (thanks!).)



gcc-14: mark amdgcn fiji deprecated
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index c817dde4..91ab8132 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -178,6 +178,16 @@ a work-in-progress.

  

+AMD Radeon (GCN)
+
+
+  The Fiji device support is now deprecated and will be removed from a
+  future release.  The default compiler configuration no longer uses Fiji
+  as the default device, and no longer includes the Fiji libraries.  Both
+  can be restored by configuring with --with-arch=fiji.
+  The default device architecture is now gfx900 (Vega).
+


Can you add ... around the "--with-arch=fiji"? Linking to

https://gcc.gnu.org/install/specific.html#amdgcn-x-amdhsa

I think that page is helpful (once the cron job has updated that page).

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".

Thanks,

Tobias



+
  

  

-
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 
München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas 
Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht 
München, HRB 106955

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

[Andrew Stubbs]

OK to commit?

Andrewgcc-14: mark amdgcn fiji deprecated


diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index c817dde4..91ab8132 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -178,6 +178,16 @@ a work-in-progress.
 
 
 
+AMD Radeon (GCN)
+
+
+  The Fiji device support is now deprecated and will be removed from a
+  future release.  The default compiler configuration no longer uses Fiji
+  as the default device, and no longer includes the Fiji libraries.  Both
+  can be restored by configuring with --with-arch=fiji.
+  The default device architecture is now gfx900 (Vega).
+
+
 
 
 

[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

[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 updated
-as new 

[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: 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: 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

Re: [PATCH] wwwdocs: Add ADL to C++ non-bugs

[Jonathan Wakely]

On Wed, 4 Oct 2023 at 20:17, Jason Merrill  wrote:
>
> On 10/3/23 10:45, Jonathan Wakely wrote:
> > We have a long history of INVALID bugs about std functions being
> > available in the global namespace (PRs 27846, 67566, 82619, 99865,
> > 110602, 111553, probably others). Let's document it.
> >
> > Also de-prioritize the C++98-only bugs, which are unlikely to affect
> > anybody nowadays.
> >
> > OK for wwwdocs?
>
> OK, thanks.
>
> Jason


After pushing it I realised the formatting looks bad compared to the
other items in the list, so I've pushed the attached follow-up as
obvious.
commit 1b1a0cf29826ce9287a203cde00fd1512918fc17
Author: Jonathan Wakely 
Date:   Thu Oct 5 10:09:54 2023 +0100

Add  to new item in C++ non-bugs list

diff --git a/htdocs/bugs/index.html b/htdocs/bugs/index.html
index 41edc561..da3d4c0d 100644
--- a/htdocs/bugs/index.html
+++ b/htdocs/bugs/index.html
@@ -541,12 +541,14 @@ for details.
 
 Functions can be called without qualifying them with their namespace.
 
+
 Argument Dependent Lookup (ADL) means that functions can be found in namespaces
 associated with their arguments. This means that move(arg) can
 call std::move if arg is a type defined in namespace
 std, such as std::string or std::vector.
 If std::move is not the function you intended to call, use a
 qualified name such as ::move(arg) or foo::move(arg).
+
 
 
 Nested classes can access private members and types of the containing

Re: [PATCH] wwwdocs: Add ADL to C++ non-bugs

[Jason Merrill]

On 10/3/23 10:45, Jonathan Wakely wrote:

We have a long history of INVALID bugs about std functions being
available in the global namespace (PRs 27846, 67566, 82619, 99865,
110602, 111553, probably others). Let's document it.

Also de-prioritize the C++98-only bugs, which are unlikely to affect
anybody nowadays.

OK for wwwdocs?


OK, thanks.

Jason

[PATCH] wwwdocs: Add ADL to C++ non-bugs

[Jonathan Wakely]

We have a long history of INVALID bugs about std functions being
available in the global namespace (PRs 27846, 67566, 82619, 99865,
110602, 111553, probably others). Let's document it.

Also de-prioritize the C++98-only bugs, which are unlikely to affect
anybody nowadays.

OK for wwwdocs?

-- >8 --

Add ADL to C++ non-bugs

Also move the item about C++98 'export' to the end, and update the item
about <: digraphs that only applies to C++98.

---
 htdocs/bugs/index.html | 36 
 1 file changed, 24 insertions(+), 12 deletions(-)

diff --git a/htdocs/bugs/index.html b/htdocs/bugs/index.html
index 813b78c0..41edc561 100644
--- a/htdocs/bugs/index.html
+++ b/htdocs/bugs/index.html
@@ -539,15 +539,15 @@ for details.
 C++
 
 
-export
-Most C++ compilers (G++ included) never implemented C++98
-export, which was removed in C++11, and the keyword reused in
-C++20 by the Modules feature. The C++98 feature was intended to support
-separate compilation of template declarations and
-definitions. Without export, a template definition must be in
-scope to be used. The obvious workaround is simply to place all definitions in
-the header itself. Alternatively, the compilation unit containing template
-definitions may be included from the header.
+Functions can be called without qualifying them with their namespace.
+
+Argument Dependent Lookup (ADL) means that functions can be found in namespaces
+associated with their arguments. This means that move(arg) can
+call std::move if arg is a type defined in namespace
+std, such as std::string or std::vector.
+If std::move is not the function you intended to call, use a
+qualified name such as ::move(arg) or foo::move(arg).
+
 
 Nested classes can access private members and types of the containing
 class.
@@ -597,9 +597,9 @@ handler and catch it in the main thread.
 If you have a class in the global namespace, say named X,
 and want to give it as a template argument to some other class, say
 std::vector, then std::vector::X
-fails with a parser error.
+fails with a parser error in C++98/C++03 mode.
 
-The reason is that the standard mandates that the sequence
+The reason is that the C++98 standard mandates that the sequence
 : is treated as if it were the token [.
 (There are several such combinations of characters - they are called
 digraphs.) Depending on the version, the compiler then reports
@@ -608,7 +608,19 @@ a parse error before the character : (the 
colon before
 
 The simplest way to avoid this is to write std::vector
 ::X, i.e. place a space between the opening angle bracket
-and the scope operator.
+and the scope operator, or compile using C++11 or later. Defect report 1104
+changed the parser rules so that :: works as expected.
+
+
+export
+Most C++ compilers (G++ included) never implemented C++98
+export, which was removed in C++11, and the keyword reused in
+C++20 by the Modules feature. The C++98 feature was intended to support
+separate compilation of template declarations and
+definitions. Without export, a template definition must be in
+scope to be used. The obvious workaround is simply to place all definitions in
+the header itself. Alternatively, the compilation unit containing template
+definitions may be included from the header.
 
 
 Common problems when upgrading the compiler
-- 
2.41.0

Re: [wwwdocs, committed] gcc-14/changes.html (OpenMP): Tweak manual-update wording

[Gerald Pfeifer]

On Mon, 25 Sep 2023, Tobias Burnus wrote:
> The 'description' words looked a bit misplaced when reading the full 
> sentence. Likewise "the libnuma" - I changed that to simply "libnuma". 
> (Alternatives would be "the libnuma library" or "the numa library".)
> 
> Hence, I fixed my own wording :-)

Looks good (for the record).

Thanks,
Gerald

[wwwdocs, committed] gcc-14/changes.html (OpenMP): Tweak manual-update wording

[Tobias Burnus]

The 'description' words looked a bit misplaced when reading the full sentence.
Likewise "the libnuma" - I changed that to simply "libnuma". (Alternatives 
would be
"the libnuma library" or "the numa library".)

Hence, I fixed my own wording :-)

Committed as attached. See also https://gcc.gnu.org/gcc-14/changes.html

Tobias
-
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 
München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas 
Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht 
München, HRB 106955
commit 50c5c9f94be7b26a2853f64909fa61ebf60086aa
Author: Tobias Burnus 
Date:   Mon Sep 25 19:36:31 2023 +0200

gcc-14/changes.html (OpenMP): Tweak manual-update wording
---
 htdocs/gcc-14/changes.html | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 2ca05ad0..c817dde4 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -74,11 +74,11 @@ a work-in-progress.
 
   The https://gcc.gnu.org/onlinedocs/libgomp/;>GNU Offloading and
   Multi Processing Runtime Library Manual has been updated and extended,
-  improving especially the ICV description, memory allocation, and the
-  description of the environment variables and OpenMP routines. On Linux,
-  the https://github.com/numactl/numactl;>libnuma is now used
-  for allocators requesting the nearest-partition trait as detailed in the
-  manual.
+  improving especially the description of ICVs, memory allocation, environment variables and OpenMP
+  routines. On Linux, https://github.com/numactl/numactl;>libnuma
+  is now used for allocators requesting the nearest-partition trait as
+  detailed in the manual.
 
   
   

[wwwdocs] OpenMP: gcc-14/changes.html and projects/gomp/ update

[Tobias Burnus]

This updates for newer features implemented very recently (project status)
and since a while (gcc-14/changes/).

Comments? Remarks? Suggestions?

I not, I plan to commit it relatively soon - but follow-up changes are
of course possible :-)

Tobias
-
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 
München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas 
Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht 
München, HRB 106955
OpenMP: gcc-14/changes.html and projects/gomp/ update

* htdocs/gcc-14/changes.html (OpenMP): Update for new features.
* htdocs/projects/gomp/index.html: Likewise, update the impl. status.
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 65382746..2ca05ad0 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -55,11 +55,30 @@ a work-in-progress.
   The requires directive's unified_address
   requirement is now fulfilled by both AMD GCN and nvptx devices.
 
+
+  OpenMP 5.1: Support was added for collapsing imperfectly nested loops and
+  using present as map-type modifier and in
+  defaultmap.
+
 
   OpenMP 5.2: The OMP_TARGET_OFFLOAD=mandatory handling has
   been updated for the clarifications and changes of the 5.2 specification.
   For Fortran, the list of directives permitted in Fortran pure procedures
-  was extended.
+  was extended. Additionally, the spec change has been implemented for
+  default implicit mapping of C/C++ pointers pointing to unmapped storage.
+
+
+  OpenMP 6.0 preview (TR11): The decl attribute is now
+  supported in C++ 11 attributes.
+
+
+  The https://gcc.gnu.org/onlinedocs/libgomp/;>GNU Offloading and
+  Multi Processing Runtime Library Manual has been updated and extended,
+  improving especially the ICV description, memory allocation, and the
+  description of the environment variables and OpenMP routines. On Linux,
+  the https://github.com/numactl/numactl;>libnuma is now used
+  for allocators requesting the nearest-partition trait as detailed in the
+  manual.
 
   
   
diff --git a/htdocs/projects/gomp/index.html b/htdocs/projects/gomp/index.html
index 04bfd908..7f0b97c3 100644
--- a/htdocs/projects/gomp/index.html
+++ b/htdocs/projects/gomp/index.html
@@ -479,8 +479,8 @@ than listed, depending on resolved corner cases and optimizations.
   
   
 allocate directive
-No
-
+GCC14
+Only C, only stack variables
   
   
 Discontiguous array section with target update construct
@@ -554,8 +554,8 @@ than listed, depending on resolved corner cases and optimizations.
   
   
 align clause in allocate directive
-No
-
+GCC14
+Only C (and only stack variables)
   
   
 align modifier in allocate clause
@@ -996,7 +996,7 @@ error.
   
   
 The decl attribute was added to the C++ attribute syntax
-No
+GCC14
 
   
   

[pushed] wwwdocs: conduct: Fix nested lists

[Gerald Pfeifer]

Looks like I never posted this push of mine from June 30th?

Just a little markup fix.

Gerald
---
 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

[wwwdocs] Document libstdc++ changes in GCC 14

[Jonathan Wakely via Gcc-patches]

Pushed to wwwdocs.


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

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index eae25f1a..65382746 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -97,7 +97,53 @@ a work-in-progress.
   
 
 
-
+Runtime Library (libstdc++)
+
+
+  
+The libstdc++exp.a library now includes all the Filesystem TS
+symbols from the libstdc++fs.a library.
+The experimental symbols for the C++23 std::stacktrace class
+are also in libstdc++exp.a, replacing the
+libstdc++_libbacktrace.a library that GCC 13 provides.
+This means that -lstdc++exp is the only library needed for
+all experimental libstdc++ features.
+  
+  Improved experimental support for C++20, including:
+
+std::chrono::parse.
+
+  
+  Improved experimental support for C++23, including:
+
+The stacktrace header is supported by default.
+
+Formatters for std::thread::id and
+  std::stacktrace.
+
+Some range adaptors now support move-only types.
+
+  
+  Experimental support for C++26, including:
+
+Native handles for filebuf, fstream, 
etc.
+std::to_string now uses std::format.
+Enhanced formatting of pointers with std::format.
+Testable result types for charconv functions.
+
+  
+  Faster numeric conversions using std::to_string and
+std::to_wstring.
+  
+  Updated parallel algorithms that are compatible with oneTBB.
+  std::numeric_limits_Float32 and
+std::numeric_limits_Float64 are now defined
+for all standard modes, not only for C++23.
+  
+  Using the std::setfill manipulator with
+std::istream is deprecated.
+  
+
 
 
 
-- 
2.41.0

[pushed] wwwdocs: *: Use "back end" instead of "backend"

[Gerald Pfeifer]

Per http://gcc.gnu.org/codingconventions.html#Spelling

Pushed.

Gerald

---
 htdocs/egcs-1.0/index.html|  2 +-
 htdocs/egcs-1.1/features.html |  2 +-
 htdocs/egcs-1.1/index.html|  2 +-
 htdocs/gcc-11/changes.html|  2 +-
 htdocs/gcc-12/changes.html|  2 +-
 htdocs/gcc-2.95/features.html |  4 ++--
 htdocs/gcc-4.9/changes.html   | 11 ++-
 htdocs/gcc-5/changes.html |  4 ++--
 htdocs/news.html  |  2 +-
 9 files changed, 16 insertions(+), 15 deletions(-)

diff --git a/htdocs/egcs-1.0/index.html b/htdocs/egcs-1.0/index.html
index 4e674440..34e44931 100644
--- a/htdocs/egcs-1.0/index.html
+++ b/htdocs/egcs-1.0/index.html
@@ -148,7 +148,7 @@ serious problems in EGCS 1.0.1.
  Add missing entries to g77 lang-options.
  Fix problem with -fpedantic in the g77 compiler.
  Fix "backspace" problem with g77 on alphas.
- Fix x86 backend problem with Fortran literals and -fpic.
+ Fix x86 back end problem with Fortran literals and -fpic.
  Fix some of the problems with negative subscripts for g77 on
  alphas.
  Fixes for Fortran builds on cygwin32/mingw32.
diff --git a/htdocs/egcs-1.1/features.html b/htdocs/egcs-1.1/features.html
index b72445a7..259abd5b 100644
--- a/htdocs/egcs-1.1/features.html
+++ b/htdocs/egcs-1.1/features.html
@@ -63,7 +63,7 @@
 x86: Alignment of static store data and jump targets is per
Intel recommendations now.  Various improvements throughout the
x86 port to improve performance on Pentium processors (including
-improved epilogue sequences for Pentium chips and backend
+improved epilogue sequences for Pentium chips and back end
 improvements which should help register allocation on all x86
 variants.  Conditional move support has been fixed and enabled for
 PPro processors.
diff --git a/htdocs/egcs-1.1/index.html b/htdocs/egcs-1.1/index.html
index adeffd37..5db4e342 100644
--- a/htdocs/egcs-1.1/index.html
+++ b/htdocs/egcs-1.1/index.html
@@ -92,7 +92,7 @@ EGCS 1.1:
  Fix a few arm code generation bugs.
  Fixincludes will fix additional broken SCO OpenServer header 
  files.
- Fix a m68k backend bug which caused invalid offsets in reg+d 
+ Fix a m68k back end bug which caused invalid offsets in reg+d 
  addresses.
  Fix problems with 64bit AIX 4.3 support.
  Fix handling of long longs for varargs/stdarg functions on the 
diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index 44389172..a00637c6 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -777,7 +777,7 @@ You may also want to check out our
 
   A number of new CPUs are supported through arguments to the
   -mcpu and -mtune options in both
-  the arm and aarch64 backends (GCC identifiers in parentheses):
+  the arm and aarch64 back ends (GCC identifiers in parentheses):
 
   Arm Cortex-A78 (cortex-a78).
   Arm Cortex-A78AE (cortex-a78ae).
diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index b10f2aa4..b4e29d72 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -755,7 +755,7 @@ function Multiply (S1, S2 : Sign) return Sign is
 BPF
 
   Support for CO-RE (compile-once, run-everywhere) has been added
-  to the BPF backend.  CO-RE allows to compile portable BPF
+  to the BPF back end.  CO-RE allows to compile portable BPF
   programs that are able to run among different versions of the
   Linux kernel.
   
diff --git a/htdocs/gcc-2.95/features.html b/htdocs/gcc-2.95/features.html
index 0e4f6c47..98ca0dd4 100644
--- a/htdocs/gcc-2.95/features.html
+++ b/htdocs/gcc-2.95/features.html
@@ -49,7 +49,7 @@
   
   New Targets and Target Specific Improvements
   
-SPARC backend rewrite.
+SPARC back end rewrite.
 -mschedule=8000 will optimize code for PA8000 class processors;
  -mpa-risc-2-0 will generate code for PA2.0 processors
 Various micro-optimizations for the ia32 port. K6 optimizations
@@ -200,7 +200,7 @@ enabled by default in future releases.  Use the option
 
Work around bug in Sun V5.0 compilers which caused bootstrap
comparison failures on SPARC targets.
-   Fix SPARC backend bug which caused aborts in final.c.
+   Fix SPARC back end bug which caused aborts in final.c.
Fix sparc-hal-solaris2* configuration fragments.
Fix bug in sparc block profiling.
Fix obscure code generation bug for the PARISC targets.
diff --git a/htdocs/gcc-4.9/changes.html b/htdocs/gcc-4.9/changes.html
index 9090c0ea..26d4843a 100644
--- a/htdocs/gcc-4.9/changes.html
+++ b/htdocs/gcc-4.9/changes.html
@@ -498,10 +498,10 @@ auto incr(T x) { return x++; }
been added. The Advanced SIMD intrinsics have also been improved.
  
   The new local register allocator (LRA) is now on by default
-   for the AArch64 backend.
+   for the AArch64 back end.
  
   The REE (Redundant extension 

[pushed] wwwdocs: gcc-12: Improve language around vectorizer and -O2

[Gerald Pfeifer]

Pushed.

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

diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
index 3816d06f..b10f2aa4 100644
--- a/htdocs/gcc-12/changes.html
+++ b/htdocs/gcc-12/changes.html
@@ -127,10 +127,12 @@ You may also want to check out our
 General Improvements
 
 
-  Vectorization is enabled at -O2 which is now equivalent to 
the
-  original -O2 -ftree-vectorize -fvect-cost-model=very-cheap.
-  Note that default vectorizer cost model has been changed which used to 
behave
-  as -fvect-cost-model=cheap were specified.
+  Vectorization is enabled at -O2 which is now
+  equivalent to what would have been
+  -O2 -ftree-vectorize -fvect-cost-model=very-cheap
+  in the past. Note that the default vectorizer cost model has
+  been changed; it used to behave as if
+  -fvect-cost-model=cheap had been specified.
   
   
 GCC now supports the
-- 
2.41.0

Re: [wwwdocs] projects/gomp: Update implementation status and minor fixes

[Gerald Pfeifer]

On Fri, 25 Aug 2023, Tobias Burnus wrote:
> It also fixes a couple of bugs and adds links providing more details
> for two items (a PR link as in libgomp.texi and a section in the manual).

Nice changes, thanks.

+Some are only stubs; see manual (

[wwwdocs] projects/gomp: Update implementation status and minor fixes

[Tobias Burnus]

This syncs the libgomp.texi implementation status to the webpage,
i.e. adding a few new items + marking some as 'supported'.

It also fixes a couple of bugs and adds links providing more details
for two items (a PR link as in libgomp.texi and a section in the manual).

Comments? Suggestions? If not, I will commit it tomorrow.

Current version: https://gcc.gnu.org/projects/gomp/
General suggestions about this page - like what to add, split off,
move around are also welcome. (Likewise comments to


Tobias

PS: The patch assumes that's Sandra's intervening-code support patch is
applied (should happen in a few hours).

PPS: The GCC 14 release notes still need to be updated to match the
current support. Alas, that's an on going theme as features keep getting
added :-)
-
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 
München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas 
Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht 
München, HRB 106955
projects/gomp/: Update implementation status and minor fixes

diff --git a/htdocs/projects/gomp/index.html b/htdocs/projects/gomp/index.html
index 2df67403..04bfd908 100644
--- a/htdocs/projects/gomp/index.html
+++ b/htdocs/projects/gomp/index.html
@@ -38,7 +38,9 @@ OpenMP and OpenACC are supported with GCC's C, C++ and Fortran compilers.
   To enable https://www.openmp.org;>OpenMP,
   use https://gcc.gnu.org/onlinedocs/gcc/C-Dialect-Options.html#index-fopenmp;
-  >-fopenmp. -fopenmp-simd can be used
+  >-fopenmp. https://gcc.gnu.org/onlinedocs/gcc/C-Dialect-Options.html#index-fopenmp-simd;>
+  -fopenmp-simd can be used
   to enable only the SIMD vectorization and loop-transformation constructs
   without creating multiple threads, offloading code or adding a library
   dependency.
@@ -75,8 +77,8 @@ OpenMP and OpenACC are supported with GCC's C, C++ and Fortran compilers.
   https://www.openmp.org/specifications/;>OpenMP specification,
   including OpenMP API examples documents, reference cards and additional
   definitions specification.
-  https://www.openacc.org/specification;>OpenACC
-  specification.
+  https://www.openacc.org/specification;>OpenACC
+  specification.
   Related GCC wiki pages: https://gcc.gnu.org/wiki/openmp;
   >openmp, https://gcc.gnu.org/wiki/OpenACC;>OpenACC,
   https://gcc.gnu.org/wiki/Offloading;>Offloading.
@@ -312,7 +314,7 @@ than listed, depending on resolved corner cases and optimizations.
 
   GCC9
   GCC12
-  GCC13
+  GCC13
   GCC14
 
 
@@ -371,12 +373,13 @@ than listed, depending on resolved corner cases and optimizations.
   
 Predefined memory spaces, memory allocators, allocator traits
 GCC11
-Some are only stubs
+Some are only stubs; see manual (https://gcc.gnu.org/onlinedocs/libgomp/Memory-allocation.html;>mainline)
   
   
 Non-rectangular loop nests
 GCC11GCC13
-C/C++ (full)Fortran (partial)
+C/C++ (full)Fortran (partial, https://gcc.gnu.org/PR110735;>PR110735)
   
   
 Nested-parallel changes to max-active-levels-var ICV
@@ -446,7 +449,7 @@ than listed, depending on resolved corner cases and optimizations.
   
   
 Mapping of Fortran pointer and allocatable variables, including pointer and allocatable components of variables
-GCC12
+GCC12
 Mapping of vars with allocatable components unsupported
   
   
@@ -471,7 +474,7 @@ than listed, depending on resolved corner cases and optimizations.
   
   
 Collapse of associated loops that are imperfectly nested loops
-No
+GCC14
 
   
   
@@ -610,7 +613,7 @@ than listed, depending on resolved corner cases and optimizations.
 
   
   
-OMP_NUM_TEAMS and OMP_TEAMS_THREAD_LIMIT env variables
+OMP_NUM_TEAMS and OMP_TEAMS_THREAD_LIMIT environment variables
 GCC12
 
   
@@ -746,6 +749,26 @@ than listed, depending on resolved corner cases and optimizations.
 No
 
   
+  
+Optional comma between directive and clause in the #pragma form
+No
+
+  
+  
+indirect clause in declare target
+No
+
+  
+  
+device_type(nohost)/device_type(host) for variables
+No
+
+  
+  
+present modifier to the map, to and from clauses
+GCC14
+
+  
   
 ompt_sync_region_t enum additions
 No
@@ -818,12 +841,12 @@ than listed, depending on resolved corner cases and optimizations.
   
   
 declare mapper with iterator and present modifiers
-No
+GCC14
 
   
   
 If a matching mapped list item is not found in the data environment, the pointer retains its original value
-No
+GCC14
 
   
   
@@ -838,7 +861,7 @@ than listed, depending on resolved corner cases and optimizations.
   
   
 Extended list of directives permitted in Fortran pure procedures
-GCC14
+GCC14
 
   
   
@@ -928,7 +951,12 @@ than listed, depending on resolved corner cases and optimizations.
   
   
 Initial value of default-device-var ICV with 

[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] [gcc-wwwdocs]gcc-13/14: Mention Intel new ISA and march support

[Richard Biener via Gcc-patches]

On Mon, Jul 17, 2023 at 5:34 AM Haochen Jiang via Gcc-patches
 wrote:
>
> Hi all,
>
> This patch adds documentation to wwwdocs to mention the recent introduction
> of Intel new ISA and march.
>
> Ok for trunk?

OK.

> BRs,
> Haochen
>
> ---
>  htdocs/gcc-13/changes.html |  4 
>  htdocs/gcc-14/changes.html | 34 +-
>  2 files changed, 37 insertions(+), 1 deletion(-)
>
> diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
> index 39414e18..68e8c5cc 100644
> --- a/htdocs/gcc-13/changes.html
> +++ b/htdocs/gcc-13/changes.html
> @@ -593,6 +593,10 @@ You may also want to check out our
>
>GCC now supports the Intel CPU named Granite Rapids through
>  -march=graniterapids.
> +The switch enables the AMX-FP16, PREFETCHI ISA extensions.
> +  
> +  GCC now supports the Intel CPU named Granite Rapids D through
> +-march=graniterapids-d.
>  The switch enables the AMX-FP16, PREFETCHI and AMX-COMPLEX ISA 
> extensions.
>
>GCC now supports AMD CPUs based on the znver4 core
> diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
> index 3f797642..dad1ba53 100644
> --- a/htdocs/gcc-14/changes.html
> +++ b/htdocs/gcc-14/changes.html
> @@ -108,7 +108,39 @@ a work-in-progress.
>
>  
>
> -
> +IA-32/x86-64
> +
> +  New ISA extension support for Intel AVX-VNNI-INT16 was added.
> +  AVX-VNNI-INT16 intrinsics are available via the 
> -mavxvnniint16
> +  compiler switch.
> +  
> +  New ISA extension support for Intel SHA512 was added.
> +  SHA512 intrinsics are available via the -msha512
> +  compiler switch.
> +  
> +  New ISA extension support for Intel SM3 was added.
> +  SM3 intrinsics are available via the -msm3
> +  compiler switch.
> +  
> +  New ISA extension support for Intel SM4 was added.
> +  SM4 intrinsics are available via the -msm4
> +  compiler switch.
> +  
> +  GCC now supports the Intel CPU named Arrow Lake through
> +-march=arrowlake.
> +Based on Alder Lake, the switch further enables the AVX-IFMA,
> +AVX-VNNI-INT8, AVX-NE-CONVERT and CMPccXADD ISA extensions.
> +  
> +  GCC now supports the Intel CPU named Arrow Lake S through
> +-march=arrowlake-s.
> +Based on Arrow Lake, the switch further enables the AVX-VNNI-INT16, 
> SHA512,
> +SM3 and SM4 ISA extensions.
> +  
> +  GCC now supports the Intel CPU named Lunar Lake through
> +-march=lunarlake.
> +Lunar Lake is based on Arrow Lake S.
> +  
> +
>
>  
>
> --
> 2.31.1
>