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  1f5a04fc5185de5ffa32fbd58194510b866adfc4 (commit)
      from  532a2e4cfb0b4f840f3568b00f277510be2fc287 (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 1f5a04fc5185de5ffa32fbd58194510b866adfc4
Author: Gerald Pfeifer <[email protected]>
Date:   Wed Oct 8 02:17:42 2025 +0200

    gcc-2.95:2.95: Use proper casing for VxWorks

diff --git a/htdocs/gcc-2.95/features.html b/htdocs/gcc-2.95/features.html
index b696c6bb..ee7fd333 100644
--- a/htdocs/gcc-2.95/features.html
+++ b/htdocs/gcc-2.95/features.html
@@ -63,7 +63,7 @@
     <li>SparcLite86x</li>
     <li>sh4</li>
     <li>Support for new systems (OpenBSD, FreeBSD, UWIN, Interix, 
arm-linux)</li>
-    <li>vxWorks targets include support for vxWorks threads</li>
+    <li>VxWorks targets include support for VxWorks threads</li>
     <li>StrongARM 110 and ARM9 support added.  ARM Scheduling parameters
     rewritten.</li>
     <li>Various changes to the MIPS port to avoid assembler macros, which
@@ -125,7 +125,7 @@
        <li> Fix compiler abort in new cfg code exposed by x86 port.</li>
        <li> Fix out of range array reference in code convert flat
             registers to the x87 stacked FP register file.</li>
-       <li> Fix minor vxworks configuration bug.</li>
+       <li> Fix minor VxWorks configuration bug.</li>
        <li> Fix return type of bsearch for SunOS 4.x.</li>
     </ul></li>
   <li> Language &amp; Runtime specific fixes.

-----------------------------------------------------------------------

Summary of changes:
 htdocs/gcc-2.95/features.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs

Reply via email to