public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/61847] bug in gfortran runtime: digits cut off when reading floating point number
Date: Fri, 25 Jul 2014 22:04:00 -0000 [thread overview]
Message-ID: <bug-61847-4-rdwu2YEzRg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61847-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61847
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |jvdelisle at gcc dot gnu.org
Severity|normal |enhancement
--- Comment #17 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
I have a patch in the works. The idea is to query the locale at the time the
Unit is connected and save the LC_NUMERIC character in the unit structure.
Then, if the decimal character matches the DECIMAL_STATUS (decimal="point" or
decimal="comma") active at the time of reading, change the decimal character
internally to the current locale character previously saved. This way, only one
call to locale is needed per unit connection, preserving efficiency. The real
string will then be converted correctly, regardless of locale.
next prev parent reply other threads:[~2014-07-25 22:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-61847-4@http.gcc.gnu.org/bugzilla/>
2014-07-19 6:19 ` [Bug fortran/61847] bug in gfortran runtime on OSX: " jvdelisle at gcc dot gnu.org
2014-07-21 15:41 ` e2cd58e1 at opayq dot com
2014-07-21 17:50 ` kargl at gcc dot gnu.org
2014-07-21 17:55 ` e2cd58e1 at opayq dot com
2014-07-21 17:58 ` kargl at gcc dot gnu.org
2014-07-21 18:18 ` e2cd58e1 at opayq dot com
2014-07-21 18:26 ` sgk at troutmask dot apl.washington.edu
2014-07-21 18:33 ` e2cd58e1 at opayq dot com
2014-07-21 19:50 ` [Bug fortran/61847] bug in gfortran runtime: " dominiq at lps dot ens.fr
2014-07-22 1:40 ` jvdelisle at gcc dot gnu.org
2014-07-22 2:07 ` e2cd58e1 at opayq dot com
2014-07-22 3:29 ` jvdelisle at gcc dot gnu.org
2014-07-22 4:28 ` jvdelisle at gcc dot gnu.org
2014-07-22 4:46 ` sgk at troutmask dot apl.washington.edu
2014-07-25 22:04 ` jvdelisle at gcc dot gnu.org [this message]
2014-08-02 21:12 ` jvdelisle at gcc dot gnu.org
2014-08-19 20:50 ` jb at gcc dot gnu.org
2014-11-03 11:02 ` burnus at gcc dot gnu.org
2014-11-04 12:35 ` jb at gcc dot gnu.org
2014-11-05 10:51 ` jb at gcc dot gnu.org
2014-11-10 0:18 ` jb at gcc dot gnu.org
2014-11-10 0:21 ` jb 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=bug-61847-4-rdwu2YEzRg@http.gcc.gnu.org/bugzilla/ \
--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: 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).