From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jeff Law <law@redhat.com>, Jerry DeLisle <jvdelisle@charter.net>,
Fritz Reese <fritzoreese@gmail.com>,
Janne Blomqvist <blomqvist.janne@gmail.com>,
Fortran List <fortran@gcc.gnu.org>
Subject: Re: Desire to allocate bit in DT_PARM bitmask for DEC FORMAT compatibility purposes
Date: Mon, 26 Mar 2018 19:15:00 -0000 [thread overview]
Message-ID: <20180326191522.GA49327@troutmask.apl.washington.edu> (raw)
In-Reply-To: <20180326074240.GP8577@tucnak>
On Mon, Mar 26, 2018 at 09:42:40AM +0200, Jakub Jelinek wrote:
> On Sun, Mar 25, 2018 at 08:44:41PM -0700, Steve Kargl wrote:
> > Now that you mention it, -std=dec would prevent a user from
> > specifically requesting, say, only Fortran 95 with DEC
> > extensions (i.e, -std=f95 -fdec).
> >
> > So, to prevent a bikeshed and micro-engineering, I think you
> > should go with using bit 28 to comunicate with the runtime
> > and put everything under -fdec in the FE.
>
> In that case, we would have two bits that are always set based on flag_dec
> in the compiler.
>
> Thus, wouldn't following patch be better? I.e. just rename the existing bit
> from a single particular DEC extension to indicate it turns on all runtime
> DEC extensions we support, now or in the future?
>
> Is this ok for trunk now (if it passes bootstrap/regtest)? Jeff then can
> follow with his patch in stage1 just using this bit.
>
Jakub,
I'll going to be traveling for meetings over he next
week, so will only have limited time and email access.
I will defer to Jerry as he is much more familiar with
the runtime library IO routines.
--
Steve
next prev parent reply other threads:[~2018-03-26 19:15 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
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 [this message]
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=20180326191522.GA49327@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=fritzoreese@gmail.com \
--cc=jakub@redhat.com \
--cc=jvdelisle@charter.net \
--cc=law@redhat.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).