public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/35862] [F2003] Implement new rounding modes for run time Date: Tue, 15 Apr 2008 21:00:00 -0000 [thread overview] Message-ID: <20080415205926.5619.qmail@sourceware.org> (raw) In-Reply-To: <bug-35862-10743@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from fxcoudert at gcc dot gnu dot org 2008-04-15 20:59 ------- (In reply to comment #4) > Well, I would argue that this digit is the most important for rounding... Only for list-directed output and if people use really large formats (which is a lot of cases). Otherwise, not. > Does this mean we have to roll out our own implementation which replaces > snprintf? Might be. > I probably miss something, but where on input do you need to round? Rounding is done for all I/O, including input. For example, if you have: read ("0.1", *, rounding="up") x read ("0.1", *, rounding="down") y then you will have x == nearest(y, -1.) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35862
next prev parent reply other threads:[~2008-04-15 21:00 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-04-07 22:34 [Bug libfortran/35862] New: " jvdelisle at gcc dot gnu dot org 2008-04-08 8:50 ` [Bug libfortran/35862] " burnus at gcc dot gnu dot org 2008-04-09 5:15 ` jvdelisle at gcc dot gnu dot org 2008-04-15 14:03 ` fxcoudert at gcc dot gnu dot org 2008-04-15 19:09 ` burnus at gcc dot gnu dot org 2008-04-15 21:00 ` fxcoudert at gcc dot gnu dot org [this message] 2009-09-29 2:45 ` jvdelisle at gcc dot gnu dot org 2009-09-29 2:48 ` jvdelisle at gcc dot gnu dot org 2009-09-29 2:51 ` jvdelisle at gcc dot gnu dot org 2009-10-01 1:37 ` jvdelisle at gcc dot gnu dot org 2009-10-01 7:35 ` burnus at gcc dot gnu dot org 2009-10-01 20:18 ` dominiq at lps dot ens dot fr 2009-10-02 2:32 ` jvdelisle at gcc dot gnu dot org 2009-10-03 15:11 ` jvdelisle at gcc dot gnu dot org 2009-10-03 16:17 ` jvdelisle at gcc dot gnu dot org 2009-10-06 3:08 ` jvdelisle at gcc dot gnu dot org 2009-10-06 3:12 ` jvdelisle at gcc dot gnu dot org 2009-10-10 15:45 ` danglin at gcc dot gnu dot org 2009-10-10 16:03 ` jvdelisle at verizon dot net 2009-10-10 17:55 ` jvdelisle at gcc dot gnu dot org 2009-10-10 18:57 ` jvdelisle at gcc dot gnu dot org 2009-10-10 23:02 ` jvdelisle at gcc dot gnu dot org 2009-10-31 1:44 ` jvdelisle at gcc dot gnu dot org 2010-07-12 8:07 ` burnus at gcc dot gnu dot org [not found] <bug-35862-4@http.gcc.gnu.org/bugzilla/> 2013-07-04 10:08 ` burnus at gcc dot gnu.org 2013-07-04 16:04 ` burnus at gcc dot gnu.org 2013-07-17 9:06 ` burnus at gcc dot gnu.org 2013-07-17 9:39 ` ubizjak at gmail dot com 2013-07-21 11:57 ` burnus at gcc dot gnu.org 2013-07-21 12:02 ` burnus at gcc dot gnu.org
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=20080415205926.5619.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).