public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jb at gcc dot gnu.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: Sat, 28 May 2011 08:41:00 -0000 [thread overview] Message-ID: <bug-19155-4-y5SavToiyh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-19155-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19155 Janne Blomqvist <jb at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED URL|http://gcc.gnu.org/ml/fortr |http://gcc.gnu.org/ml/gcc-p |an/2005-06/msg00318.html |atches/2011-05/msg02224.htm | |l CC| |jb at gcc dot gnu.org Resolution|FIXED | AssignedTo|fxcoudert at gcc dot |jb at gcc dot gnu.org |gnu.org | --- Comment #27 from Janne Blomqvist <jb at gcc dot gnu.org> 2011-05-28 08:22:14 UTC --- Reopening, since the EINVAL thing is causing problems on HP-UX 11.31. Assigning to myself, patch at http://gcc.gnu.org/ml/gcc-patches/2011-05/msg02224.html
next parent reply other threads:[~2011-05-28 8:23 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-19155-4@http.gcc.gnu.org/bugzilla/> 2011-05-28 8:41 ` jb at gcc dot gnu.org [this message] 2011-05-29 9:03 ` jb at gcc dot gnu.org 2011-05-29 9:35 ` jb at gcc dot gnu.org 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 2005-06-12 20:05 ` [Bug libfortran/19155] [4.0 only] blanks not treated as zeros in 'E' format read (NIST FM110.FOR) 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 2005-06-17 16:25 ` fxcoudert at gcc dot gnu dot 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-19155-4-y5SavToiyh@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: 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).