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:12:00 -0000 [thread overview]
Message-ID: <be879428-595e-b3e4-e663-37c0e6d65b34@redhat.com> (raw)
In-Reply-To: <20180323083853.GK5866@tucnak>
On 03/23/2018 02:38 AM, Jakub Jelinek wrote:
> On Fri, Mar 23, 2018 at 09:12:21AM +0100, Jakub Jelinek wrote:
>>> I have some philosophical questions.
>>>
>>> 1) Why do you want 15, 7, 2? Why is this so critical?
>>
>> Because that is what all those compilers document and agree on.
>> See e.g.
>> https://software.intel.com/en-us/node/678750#32937290-265D-4805-B2B7-4E78F6AAD0D8
>> for Intel documentation, I'm sure Jeff has links to other documentations.
>
> BTW, it seems libgfortran already has a similar extension, at least my
> reading of the standards (checked 97 and 2003) is that for Lw the standard
> doesn't allow omitting the width, but we allow that as extension:
> else
> {
> fmt->saved_token = t;
> notify_std (&dtp->common, GFC_STD_GNU,
> "Positive width required with L descriptor");
> }
> fmt->value = 1; /* Default width */
> (and sadly different from what Intel Fortran does, because it uses 2).
> Wonder about other compilers, if they all agree on 2, perhaps we should
> behave above differently based on the new bit?
Yup. I saw that too in my wanderings. I was hoping it was actually
more general and that we could piggy-back a bit. But that wasn't the
case AFAICT.
jeff
next prev parent reply other threads:[~2018-03-23 19:12 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 [this message]
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
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=be879428-595e-b3e4-e663-37c0e6d65b34@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).