Re: [Patch, gcc-wwdocs] Update to Fortran changes

2019-11-28 Thread Gerald Pfeifer
On Tue, 26 Nov 2019, Mark Eggleston wrote: > Second attempt this time with attachment. >From f884924877ba84578e75bd16cb127bab33eb5ee6 Mon Sep 17 00:00:00 2001 From: Mark Eggleston Date: Tue, 26 Nov 2019 10:12:44 + Subject: [PATCH] Update Fortran changes + +A blank format item

Making things a bit easier (was: [Patch, gcc-wwdocs] Update to Fortran changes)

2019-11-28 Thread Gerald Pfeifer
On Tue, 26 Nov 2019, Mark Eggleston wrote: > I've check the changes with W3 validator. There are no problems related > to my changes, however, it does object to the lack of character encoding > in the file. My knowledge of HTML is limited, so don't know how to fix > that. Let me take this as

Re: [Patch, gcc-wwdocs] Update to Fortran changes

2019-11-27 Thread Mark Eggleston
On 27/11/2019 08:29, Tobias Burnus wrote: On 11/27/19 8:58 AM, Janne Blomqvist wrote: On Tue, Nov 26, 2019 at 1:12 PM Tobias Burnus wrote: AUTOMATIC attribute Speaking of which, to avoid confusion maybe we should rename the -f[no-]automatic option to something like -f[no-]save, since the

Re: [Patch, gcc-wwdocs] Update to Fortran changes

2019-11-27 Thread Mark Eggleston
Corrected and committed. On 27/11/2019 09:00, Tobias Burnus wrote: On 11/26/19 7:33 PM, Mark Eggleston wrote:   htdocs/gcc-10/changes.html | 41 + +  +    Default fields widths can be used for I, F +    and G format specifiers when

Re: [Patch, gcc-wwdocs] Update to Fortran changes

2019-11-27 Thread Tobias Burnus
On 11/26/19 7:33 PM, Mark Eggleston wrote: htdocs/gcc-10/changes.html | 41 + + +Default fields widths can be used for I, F +and G format specifiers when excplicit widths are omitted. +Use the option -fdec-format-defaults,

Re: [Patch, gcc-wwdocs] Update to Fortran changes

2019-11-27 Thread Janne Blomqvist
On Wed, Nov 27, 2019 at 10:29 AM Tobias Burnus wrote: > > On 11/27/19 8:58 AM, Janne Blomqvist wrote: > > On Tue, Nov 26, 2019 at 1:12 PM Tobias Burnus > > wrote: > >> AUTOMATIC attribute > > Speaking of which, to avoid confusion maybe we should rename the > > -f[no-]automatic option to

Re: [Patch, gcc-wwdocs] Update to Fortran changes

2019-11-27 Thread Tobias Burnus
On 11/27/19 8:58 AM, Janne Blomqvist wrote: On Tue, Nov 26, 2019 at 1:12 PM Tobias Burnus wrote: AUTOMATIC attribute Speaking of which, to avoid confusion maybe we should rename the -f[no-]automatic option to something like -f[no-]save, since the Fortran standard description of an "automatic

Re: [Patch, gcc-wwdocs] Update to Fortran changes

2019-11-26 Thread Janne Blomqvist
On Tue, Nov 26, 2019 at 1:12 PM Tobias Burnus wrote: > In particular, currently, the following item does not make clear that it > is about legacy support: "Variables with the AUTOMATIC > attribute can be used in EQUIVALENCE statements." > > I think it can remain as is with the -fdec umbrella

Re: [Patch, gcc-wwdocs] Update to Fortran changes

2019-11-26 Thread Mark Eggleston
Second attempt this time with attachment. Apologies. regards, Mark On 26/11/2019 15:56, Mark Eggleston wrote: On 26/11/2019 11:12, Tobias Burnus wrote: Hi Mark, On 11/26/19 11:46 AM, Mark Eggleston wrote: I've check the changes with W3 validator. There are no problems related to my

Re: [Patch, gcc-wwdocs] Update to Fortran changes

2019-11-26 Thread Mark Eggleston
On 26/11/2019 11:12, Tobias Burnus wrote: Hi Mark, On 11/26/19 11:46 AM, Mark Eggleston wrote: I've check the changes with W3 validator. There are no problems related to my changes, however, it does object to the lack of character encoding in the file. Note that some script modifies the

Re: [Patch, gcc-wwdocs] Update to Fortran changes

2019-11-26 Thread Tobias Burnus
Hi Mark, On 11/26/19 11:46 AM, Mark Eggleston wrote: I've check the changes with W3 validator. There are no problems related to my changes, however, it does object to the lack of character encoding in the file. Note that some script modifies the file a bit – the final file does have a

[Patch, gcc-wwdocs] Update to Fortran changes

2019-11-26 Thread Mark Eggleston
I've check the changes with W3 validator. There are no problems related to my changes, however, it does object to the lack of character encoding in the file. My knowledge of HTML is limited, so don't know how to fix that. This is the first time in changing the wwwdoc, I haven't included a