public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/19155] [4.0 only] blanks not treated as zeros in 'E' format read (NIST FM110.FOR) Date: Fri, 17 Jun 2005 16:24:00 -0000 [thread overview] Message-ID: <20050617162418.3626.qmail@sourceware.org> (raw) In-Reply-To: <20041225214626.19155.Thomas.Koenig@online.de> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-06-17 16:24 ------- Subject: Bug 19155 CVSROOT: /cvs/gcc Module name: gcc Branch: gcc-4_0-branch Changes by: fxcoudert@gcc.gnu.org 2005-06-17 16:23:42 Modified files: libgfortran : ChangeLog libgfortran/io : read.c Log message: PR libfortran/19155 * io/read.c (convert_real): strtod can set errno to EINVAL on an empty string, but we shouldn't have an error in that case. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.163.2.54&r2=1.163.2.55 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libgfortran/io/read.c.diff?cvsroot=gcc&only_with_tag=gcc-4_0-branch&r1=1.8.10.2&r2=1.8.10.3 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19155
next prev parent reply other threads:[~2005-06-17 16:24 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-12-25 21:46 [Bug libfortran/19155] New: blanks not treated as zeros in 'E' format read Thomas dot Koenig at online dot de 2004-12-26 19:45 ` [Bug libfortran/19155] " sgk at troutmask dot apl dot washington dot edu 2005-01-06 14:43 ` tobi at gcc dot gnu dot org 2005-01-16 23:45 ` [Bug libfortran/19155] blanks not treated as zeros in 'E' format read (NIST FM110.FOR) bdavis at gcc dot gnu dot org 2005-03-02 10:31 ` coudert at clipper dot ens dot fr 2005-03-11 21:21 ` Thomas dot Koenig at online dot de 2005-03-11 22:34 ` sgk at troutmask dot apl dot washington dot edu 2005-03-31 16:38 ` fxcoudert at gcc dot gnu dot org 2005-03-31 21:43 ` kargl at gcc dot gnu dot org 2005-04-05 9:41 ` fxcoudert at gcc dot gnu dot org 2005-05-09 11:31 ` cvs-commit at gcc dot gnu dot org 2005-05-09 11:35 ` cvs-commit at gcc dot gnu dot org 2005-05-09 11:40 ` fxcoudert at gcc dot gnu dot org 2005-05-09 21:38 ` pinskia at gcc dot gnu dot org 2005-05-16 19:45 ` dje at gcc dot gnu dot org 2005-05-16 20:19 ` fxcoudert at gcc dot gnu dot org 2005-06-02 5:45 ` fxcoudert at gcc dot gnu dot org 2005-06-12 8:05 ` fxcoudert at gcc dot gnu dot org 2005-06-12 9:21 ` fxcoudert at gcc dot gnu dot org 2005-06-12 17:48 ` kargl at gcc dot gnu dot org 2005-06-12 19:59 ` cvs-commit at gcc dot gnu dot org 2005-06-12 20:05 ` [Bug libfortran/19155] [4.0 only] " fxcoudert at gcc dot gnu dot org 2005-06-16 22:39 ` cvs-commit at gcc dot gnu dot org 2005-06-16 23:04 ` fxcoudert at gcc dot gnu dot org 2005-06-17 15:16 ` dje at gcc dot gnu dot org 2005-06-17 15:40 ` fxcoudert at gcc dot gnu dot org 2005-06-17 16:21 ` cvs-commit at gcc dot gnu dot org 2005-06-17 16:24 ` cvs-commit at gcc dot gnu dot org [this message] 2005-06-17 16:25 ` fxcoudert at gcc dot gnu dot org [not found] <bug-19155-4@http.gcc.gnu.org/bugzilla/> 2011-05-28 8:41 ` jb at gcc dot gnu.org 2011-05-29 9:03 ` jb at gcc dot gnu.org 2011-05-29 9:35 ` 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=20050617162418.3626.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).