gcc-wwwdocs branch master updated. 4662147a94753cf3803426c34151573dc2d1863a

[Simon Martin via Gcc-cvs-wwwdocs]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
   via  4662147a94753cf3803426c34151573dc2d1863a (commit)
  from  8ce27f951e79d3c0342f132fd5c20eccd4ada161 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
commit 4662147a94753cf3803426c34151573dc2d1863a
Author: Simon Martin 
Date:   Wed Oct 2 10:29:08 2024 +0200

gcc-wwwdocs: Mention check-c++-all target for C++ front end patch testing

This is a follow-up to the discussion about testing changes to the C++
front end in
https://gcc.gnu.org/pipermail/gcc-patches/2024-October/664258.html

It also clarifies that the make invocation examples should be made from
the *build* tree.

Validated fine via https://validator.w3.org.

diff --git a/htdocs/contribute.html b/htdocs/contribute.html
index 53c27c6e..3ab65323 100644
--- a/htdocs/contribute.html
+++ b/htdocs/contribute.html
@@ -111,9 +111,17 @@ For a normal native configuration, running
 make bootstrap
 make -k check
 
-from the top level of the GCC tree (not the
+from the top level of the GCC build tree (not the
 gcc subdirectory) will accomplish this.
 
+If your change is to the C++ front end, you need to run the C++ testsuite
+in all standard conformance levels. For a normal native configuration,
+running
+
+make -C gcc -k check-c++-all
+
+from the top level of the GCC build tree will accomplish this.
+
 If your change is to a front end other than the C or C++ front end,
 or a runtime library other than libgcc, you need to verify
 only that the runtime library for that language still builds and the

---

Summary of changes:
 htdocs/contribute.html | 10 +-
 1 file changed, 9 insertions(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs

[wwwdocs] FEAT_LS64 is Optional

[Mick Thomas Lim via Gcc-cvs-wwwdocs]

Regarding AArch64 Options (Using the GNU Compiler Collection 
(GCC)),

This section is stale:
‘ls64’
Enable the 64-byte atomic load and store instructions for accelerators. This 
option is enabled by default for -march=armv8.7-a.

It has already been fixed in this commit:
commit d0f8cb17bbd35e5eb25fc3b2119756b3e103e798
Author: Tamar Christina 
Date:   Wed Feb 21 11:42:53 2024 +

AArch64: remove ls64 from being mandatory on armv8.7-a..

The Arm Architectural Reference Manual (Version J.a, section A2.9 on 
FEAT_LS64)
shows that ls64 is an optional extensions and should not be enabled by 
default
for Armv8.7-a.


Regards,
Mick