From: Janus Weil <janus@gcc.gnu.org>
To: "Dominique d'Humières" <dominiq@lps.ens.fr>
Cc: Francisco Pena <fran.pena@usc.es>, gfortran <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: Documentation of LTIME
Date: Sat, 26 Nov 2016 17:03:00 -0000 [thread overview]
Message-ID: <CAKwh3qhf9egrL3V7+5gXZTMcBBVY2yG=bYhOtmnSB5AHfkPGYQ@mail.gmail.com> (raw)
In-Reply-To: <CAKwh3qgT9iKVxT=LGbb3Mh2sf0Kc2pZSU45GQ3JSXON3HFQC_Q@mail.gmail.com>
2016-11-26 17:58 GMT+01:00 Janus Weil <janus@gcc.gnu.org>:
>>> * possibly add some more cross-links to intrinsic.texi
>>
>> Could you please elaborate?
>
> I just mean it might be useful to add some more links from LTIME to
> ITIME, IDATE and DATE_AND_DATE (and back?). They are are all very
> similar.
Sorry, I meant DATE_AND_TIME here.
>> Well LTIME cannot accept both kind(4) and kind(8) arguments. The reference to TIME8 looks like a mistake, isn’t it?
>
> Huh, in libgfortran I see two versions with different kinds (ltime_i4
> and ltime_i8), but in my tests I never get LTIME to work with kind=8
> arguments. I guess that is the real bug here ...
I think the origin of the bug is:
void
gfc_resolve_ltime (gfc_code *c)
{
c->resolved_sym
= gfc_get_intrinsic_sub_symbol (gfc_get_string (PREFIX ("ltime_i%d"),
gfc_default_integer_kind));
}
This always uses the ITIME version corresponding to
gfc_default_integer_kind, disregarding the actual kind of the
arguments.
Cheers,
Janus
next prev parent reply other threads:[~2016-11-26 17:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42E6ADCB-E228-42B0-BF2B-E630E56C2048@lps.ens.fr>
[not found] ` <CAC2FYYqEPKCNp88Yb7RTJtOZjuU1b-VirROSoCrRQgNwNRgm5Q@mail.gmail.com>
2016-11-26 15:49 ` Dominique d'Humières
2016-11-26 15:54 ` Janus Weil
2016-11-26 16:01 ` Janus Weil
2016-11-26 16:28 ` Dominique d'Humières
2016-11-26 16:58 ` Janus Weil
2016-11-26 17:03 ` Janus Weil [this message]
2016-11-26 17:17 ` Janne Blomqvist
2016-11-26 17:25 ` Janus Weil
2016-11-26 18:35 ` Dominique d'Humières
2016-11-26 20:45 ` Janus Weil
2016-12-19 10:59 ` Janus Weil
2016-11-26 16:19 ` Dominique d'Humières
2016-11-26 16:17 ` Francisco Pena
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='CAKwh3qhf9egrL3V7+5gXZTMcBBVY2yG=bYhOtmnSB5AHfkPGYQ@mail.gmail.com' \
--to=janus@gcc.gnu.org \
--cc=dominiq@lps.ens.fr \
--cc=fortran@gcc.gnu.org \
--cc=fran.pena@usc.es \
--cc=gcc-patches@gcc.gnu.org \
/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).