From: Tobias Burnus <burnus@net-b.de>
To: Jerry DeLisle <jvdelisle@charter.net>,
Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc: gfortran <fortran@gcc.gnu.org>
Subject: Re: [PATCH, libgfortran] PR68867 numeric formatting problem in the fortran library
Date: Mon, 14 Dec 2015 23:09:00 -0000 [thread overview]
Message-ID: <566F4C3B.3040304@net-b.de> (raw)
In-Reply-To: <566D021C.2080306@charter.net>
Jerry DeLisle wrote:
> On 12/12/2015 08:30 PM, Steve Kargl wrote:
>> s/103/106
> Fixed the typo, thanks.
> [...]
> The patch only affects default "list directed" formatting which is processor
> defined, ie defined by us. It seems obvious that the number of digits we emit
> should be less. [...]
>
> Still looking for an OK.
Looks good to me.
Tobias
prev parent reply other threads:[~2015-12-14 23:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-13 4:14 Jerry DeLisle
2015-12-13 4:30 ` Steve Kargl
2015-12-13 5:29 ` Jerry DeLisle
2015-12-14 23:09 ` Tobias Burnus [this message]
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=566F4C3B.3040304@net-b.de \
--to=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=jvdelisle@charter.net \
--cc=sgk@troutmask.apl.washington.edu \
/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).