From: Jeff Law <law@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>, Jerry DeLisle <jvdelisle@charter.net>
Cc: Janne Blomqvist <blomqvist.janne@gmail.com>,
Fortran List <fortran@gcc.gnu.org>,
fritzoreese@gmail.com
Subject: Re: Desire to allocate bit in DT_PARM bitmask for DEC FORMAT compatibility purposes
Date: Fri, 23 Mar 2018 19:58:00 -0000 [thread overview]
Message-ID: <380c2de1-5f32-cd3c-2f9f-ffd05e8339ef@redhat.com> (raw)
In-Reply-To: <20180323081221.GA8577@tucnak>
On 03/23/2018 02:12 AM, Jakub Jelinek wrote:
>
> We can certainly offer a warning with suggested fixit, if the compiler sees
> the format string with ommitted widths, it can warn that it is a DEC
> extension and hint how to rewrite the string with the default width so that
> users can change it (does Fortran FE also have the -fdiagnostics-generate-patch
> support?).
And I've suggested this as a way to start the process of modernizing the
format statement handling :-)
Jeff
next prev parent reply other threads:[~2018-03-23 19:58 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 18:41 Jeff Law
2018-03-21 18:35 ` Jakub Jelinek
2018-03-21 17:29 ` Jeff Law
2018-03-21 18:38 ` Janne Blomqvist
2018-03-21 19:26 ` Jeff Law
2018-03-22 5:49 ` Jeff Law
2018-03-23 2:07 ` Jerry DeLisle
2018-03-23 9:02 ` Janne Blomqvist
2018-03-23 9:08 ` Jakub Jelinek
2018-03-23 14:22 ` Jerry DeLisle
2018-03-23 9:35 ` Jakub Jelinek
2018-03-23 8:39 ` Jakub Jelinek
2018-03-23 14:46 ` Jerry DeLisle
2018-03-23 19:12 ` Jeff Law
2018-03-23 9:35 ` Jakub Jelinek
2018-03-23 13:26 ` Lukasz Kolodziejczyk
2018-03-23 14:47 ` Jerry DeLisle
2018-03-23 19:39 ` Jeff Law
2018-03-23 21:36 ` Steve Kargl
2018-03-23 19:58 ` Jeff Law [this message]
2018-03-23 21:32 ` Fritz Reese
2018-03-24 9:35 ` Jakub Jelinek
2018-03-24 16:04 ` Steve Kargl
2018-03-24 17:35 ` Jakub Jelinek
2018-03-24 17:11 ` Steve Kargl
2018-03-24 18:20 ` Jerry DeLisle
2018-03-25 18:48 ` Jeff Law
2018-03-25 19:09 ` Jerry DeLisle
2018-03-26 3:41 ` Jeff Law
2018-03-26 3:44 ` Steve Kargl
2018-03-26 7:42 ` Jakub Jelinek
2018-03-26 12:14 ` Fritz Reese
2018-03-26 19:15 ` Steve Kargl
2018-03-26 21:04 ` Jeff Law
2018-03-26 21:03 ` Jeff Law
2018-03-27 9:14 ` Jakub Jelinek
2018-03-28 1:02 ` Jerry DeLisle
2018-03-23 19:56 ` Jeff Law
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=380c2de1-5f32-cd3c-2f9f-ffd05e8339ef@redhat.com \
--to=law@redhat.com \
--cc=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=fritzoreese@gmail.com \
--cc=jakub@redhat.com \
--cc=jvdelisle@charter.net \
/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).