From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Tobias Burnus <burnus@net-b.de>
Cc: Tobias Burnus <tobias@codesourcery.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
fortran <fortran@gcc.gnu.org>,
Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: [Patch, Fortran + wwwdocs] PR93253 – Document BOZ changes, make it friendlier in legacy code
Date: Wed, 15 Jan 2020 23:57:00 -0000 [thread overview]
Message-ID: <20200115231726.GA5149@troutmask.apl.washington.edu> (raw)
In-Reply-To: <96a1ac0b-54e3-90a0-bef0-6a558b4c4905@net-b.de>
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
next prev parent reply other threads:[~2020-01-15 23:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 17:02 Tobias Burnus
2020-01-15 20:11 ` Steve Kargl
2020-01-15 22:48 ` Tobias Burnus
2020-01-15 23:57 ` Steve Kargl [this message]
2020-01-18 12:46 ` Gerald Pfeifer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200115231726.GA5149@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=tobias@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).