Re: [wwwdocs] Update changes.html with libstdc++ changes

2015-04-07 Thread Gerald Pfeifer 

On Sat, 6 Dec 2014, Jonathan Wakely wrote:

This adds recent libstdc++ updates to gcc-5/changes.html


Nice!  Just a most minor change to end a list with a full stop 
instead of a semi-colon.  Applied.


Gerald

Index: changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-5/changes.html,v
retrieving revision 1.94
diff -u -r1.94 changes.html
--- changes.html6 Apr 2015 12:56:40 -   1.94
+++ changes.html8 Apr 2015 06:54:43 -
@@ -456,7 +456,7 @@
New random number distributions logistic_distribution and
  uniform_on_sphere_distribution as extensions.
https://sourceware.org/gdb/current/onlinedocs/gdb/Xmethods-In-Python.html";>GDB
-  Xmethods for containers and std::unique_ptr;
+  Xmethods for containers and std::unique_ptr.
  

Fortran

Re: [wwwdocs] Update changes.html with libstdc++ changes

2015-04-08 Thread Gerald Pfeifer 
On Sat, 6 Dec 2014, Jonathan Wakely wrote:
> I'm also noting one old change in the GCC 4.5 page, and
> removing/changing some links to the C++0x status table. The list of
> features supported on trunk is fairly irrelevant to someone looking at
> the 4.4 release notes, so I've linked to the docs for the relevant
> release

This was a good change, thank you.

The only drawback of this, and some similar cases, is that we now
risk referring to older versions on a release branch.  I do not
have a good idea how to best handle this, so for now I updated
references to online documentation to the latest versions (4.8.4 
and 4.9.2, respectively).

Gerald

Index: gcc-4.8/changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v
retrieving revision 1.131
diff -u -r1.131 changes.html
--- gcc-4.8/changes.html19 Dec 2014 11:38:57 -  1.131
+++ gcc-4.8/changes.html8 Apr 2015 10:30:59 -
@@ -292,7 +292,7 @@
   Runtime Library (libstdc++)
 
   
-https://gcc.gnu.org/onlinedocs/gcc-4.8.3/libstdc++/manual/manual/status.html#status.iso.2011";>
+https://gcc.gnu.org/onlinedocs/gcc-4.8.4/libstdc++/manual/manual/status.html#status.iso.2011";>
Improved experimental support for the new ISO C++ standard, C++11,
including:

Index: gcc-4.9/changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.9/changes.html,v
retrieving revision 1.84
diff -u -r1.84 changes.html
--- gcc-4.9/changes.html31 Dec 2014 10:51:19 -  1.84
+++ gcc-4.9/changes.html8 Apr 2015 10:31:00 -
@@ -128,7 +128,7 @@
and starting with the 4.9.1 release also in the Fortran compiler.
The new -fopenmp-simd option can be used to enable OpenMP's
SIMD directives, while ignoring other OpenMP directives. The new https://gcc.gnu.org/onlinedocs/gcc-4.9.0/gcc/Optimize-Options.html#index-fsimd-cost-model-908";
+   
href="https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/Optimize-Options.html#index-fsimd-cost-model-908";
>-fsimd-cost-model= option permits to tune the
vectorization cost model for loops annotated with OpenMP and Cilk
Plus simd directives; -Wopenmp-simd warns when
@@ -151,7 +151,7 @@
   
 Support for colorizing diagnostics emitted by GCC has been added.
 The https://gcc.gnu.org/onlinedocs/gcc-4.9.0/gcc/Language-Independent-Options.html#index-fdiagnostics-color-252";
+
href="https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/Language-Independent-Options.html#index-fdiagnostics-color-252";
 >-fdiagnostics-color=auto will enable it when
 outputting to terminals, -fdiagnostics-color=always
 unconditionally.  The GCC_COLORS environment variable
@@ -177,7 +177,7 @@
 
 
 With the new https://gcc.gnu.org/onlinedocs/gcc-4.9.0/gcc/Loop-Specific-Pragmas.html";
+
href="https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/Loop-Specific-Pragmas.html";
 >#pragma GCC ivdep, the user can assert that there are no
 loop-carried dependencies which would prevent concurrent execution of
 consecutive iterations using SIMD (single instruction multiple data)
@@ -383,7 +383,7 @@
   ABI changes:
   
 The https://gcc.gnu.org/onlinedocs/gcc-4.9.0/gfortran/Argument-passing-conventions.html";
+  
href="https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gfortran/Argument-passing-conventions.html";
   >argument passing ABI has changed for scalar dummy
  arguments of type INTEGER, REAL,
  COMPLEX and LOGICAL, which have
@@ -418,7 +418,7 @@
   controlled by the -Wzerotrip option, which is implied by
   -Wall.
 The new NO_ARG_CHECK attribute of the https://gcc.gnu.org/onlinedocs/gcc-4.9.0/gfortran/GNU-Fortran-Compiler-Directives.html";
+  
href="https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gfortran/GNU-Fortran-Compiler-Directives.html";
   >!GCC$ directive can be used to disable the
   type-kind-rank (TKR) argument check for a dummy argument. The feature
   is similar to ISO/IEC TS 29133:2012's TYPE(*), except that
@@ -452,7 +452,7 @@
 the execution and any exception (but inexact) is signaling, a warning 
is
 printed to ERROR_UNIT, indicating which exceptions are
 signaling. The https://gcc.gnu.org/onlinedocs/gcc-4.9.0/gfortran/Debugging-Options.html";
+
href="https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gfortran/Debugging-Options.html";
 >-ffpe-summary= command-line option can be used to fine-tune
 for which exceptions the warning should be shown.
   Rounding on input (READ) is now handled on systems where
@@ -597,7 +597,7 @@
   having to compile the entire file with the -mxxx option.
   This improves the usability of x86 intrinsics and is particularly useful
   when doing https://gcc.gnu.org/onlinedocs/gcc-4.9.0/gcc/Function-Multiversioning.html";
+  
href="https://gcc.gnu.org

Re: [wwwdocs] Update changes.html with libstdc++ changes

2015-04-08 Thread Jonathan Wakely 

On 08/04/15 13:06 +0200, Gerald Pfeifer wrote:

On Sat, 6 Dec 2014, Jonathan Wakely wrote:

I'm also noting one old change in the GCC 4.5 page, and
removing/changing some links to the C++0x status table. The list of
features supported on trunk is fairly irrelevant to someone looking at
the 4.4 release notes, so I've linked to the docs for the relevant
release


This was a good change, thank you.

The only drawback of this, and some similar cases, is that we now
risk referring to older versions on a release branch.  I do not
have a good idea how to best handle this, so for now I updated
references to online documentation to the latest versions (4.8.4
and 4.9.2, respectively).


Yes, I realised that problem when making the change and linking to the
versions that were current at the time. One option would be to add a
gcc-4.8 symlink that points to the latest gcc-4.8.x version, but that
adds more work for the release managers and only has a small benefit.

Alternatively, since we only tend to have four or five releases from a
branch, we could just update them manually when we remember to. That's
only necessary until the branch closes, at which point the latest
release won't change. It's not a huge problem if the links don't go
to the latest docs immediately IMHO.

Re: [wwwdocs] Update changes.html with libstdc++ changes

2015-04-20 Thread Gerald Pfeifer 
On Wed, 8 Apr 2015, Jonathan Wakely wrote:
>> The only drawback of this, and some similar cases, is that we now
>> risk referring to older versions on a release branch.
> Yes, I realised that problem when making the change and linking to the
> versions that were current at the time. One option would be to add a
> gcc-4.8 symlink that points to the latest gcc-4.8.x version, but that
> adds more work for the release managers and only has a small benefit.

Agreed.

> Alternatively, since we only tend to have four or five releases from a
> branch, we could just update them manually when we remember to. That's
> only necessary until the branch closes, at which point the latest
> release won't change. It's not a huge problem if the links don't go
> to the latest docs immediately IMHO.

Agreed, and agreed.  Let's just keep an eye on it and (try to)
update when a new release of an existing branch comes out.

Gerald