Re: [Patch, Fortran + wwwdocs] PR93253 – Document BOZ changes, make it friendlier in legacy code

[Steve Kargl <sgk@troutmask.apl.washington.edu>]

On Wed, Jan 15, 2020 at 11:25:44PM +0100, Tobias Burnus wrote:
> 
> regarding the release-notes text: I like your version – it helps if 
> someone writes the text, who knows what changed. I have fixed a typo and 
> adapted the syntax – see attachment. Any comment to it? Otherwise, I 
> intent to commit it tomorrow.
> 
> Regarding the patch, I enclosed a revised version. Do you have more 
> suggestions – or does it look okay now?

One missing word in the release-notes.  See below.


> 
> On 1/15/20 7:56 PM, Steve Kargl wrote:
> >> +    {
> >> +      const char hint[] = ". Use %<-fallow-invalid-boz%> if you cannot fix it";
> > Suggest adding ". [See %<-fallow-invalid-boz%>.]"
> 
> Followed your suggestion.

Thanks.

> 
> >> --- a/gcc/fortran/gfortran.texi
> >> +++ b/gcc/fortran/gfortran.texi
> I have reworded it a bit.
> >> -			  "nonstandard syntax", &gfc_current_locus))
> >> +			  "nonstandard X instead of Z", &gfc_current_locus))
> > I suppose ok, but don't think a change is needed.
> I still think the new version is more helpful. Hence …

Ok.

> diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
> index caa9df70..83404a1a 100644
> --- a/htdocs/gcc-10/changes.html
> +++ b/htdocs/gcc-10/changes.html
> @@ -260,6 +260,16 @@ a work-in-progress.</p>
>      with <code>-std=legacy</code>.  <code>-Wargument-mismatch</code>
>      has been removed.
>    </li>
> +  <li>
> +    The handling of a BOZ literal constant has been reworked to provide
> +    better conformance to the Fortran 2008 and 2018 standards.  In these
> +    Fortran standards, a BOZ literal constant is a typeless and kindless
> +    entity.  As a part of the rework, documented and undocumented
> +    extensions to the Fortran standard now emit errors during compilation.
> +    Some these extensions are permitted with the

s/Some/Some of

> +    <code>-fallow-invalid-boz</code>, where the error is degraded to a
> +    warning and the code is compiled as with older gfortran.
> +  <li>
>    <li>
>      At any optimization level except<code>-Os</code>, gfortran now
>      uses inline packing for arguments instead of calling a library

Everything else looks good.

The original patch was submitted with 
https://gcc.gnu.org/ml/fortran/2019-07/msg00054.html

-- 
Steve