public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/50105] [4.6/4.7/4.8 Regression] I/O with g6.5 - wrong number of "**" shown Date: Wed, 02 Jan 2013 17:24:00 -0000 [thread overview] Message-ID: <bug-50105-4-43nd1YkT36@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50105-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50105 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #20 from Tobias Burnus <burnus at gcc dot gnu.org> 2013-01-02 17:24:12 UTC --- (In reply to comment #17) > 10.7.2.3.2 says > "the field occupies w positions, the fractional part of which > consists of d digits" > and this does not make sense if w<d. Therefore, according to the > first sentence of 1.5 Conformance, the program is not standard > conforming. > > There are therefore no requirements on the processor for this > program, and it may produce either output, or even a runtime error. > Disclaimer: WG5 might still revise the J3 answer; there will be also an J3 > email voting on the IR. Latest result version ftp://ftp.nag.co.uk/sc22wg5/N1901-N1950/N1932.txt (search for F08/0063) Result was: YES WITH COMMENTS, with 7 YES votes, 1 YES WITH COMMENT and 1 NO vote (or two? At the top it lists one, below it has two comments claiming a "NO".) ftp://ftp.nag.co.uk/sc22wg5/N1901-N1950/N1944.txt Additionally, it is listed in the Corrigendum 2 draft as being contained in the document, though no edits have been done: ftp://ftp.nag.co.uk/sc22wg5/N1901-N1950/N1948.pdf
next prev parent reply other threads:[~2013-01-02 17:24 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-17 6:22 [Bug libfortran/50105] New: Possibly: [4.3/4.4/4.5/4.6/4.7 " burnus at gcc dot gnu.org 2011-08-17 6:40 ` [Bug libfortran/50105] " burnus at gcc dot gnu.org 2011-08-17 7:34 ` burnus at gcc dot gnu.org 2011-08-17 7:53 ` thenlich at users dot sourceforge.net 2011-08-17 9:14 ` [Bug libfortran/50105] Possibly: [4.6/4.7 " burnus at gcc dot gnu.org 2011-08-17 13:27 ` burnus at gcc dot gnu.org 2011-08-18 8:59 ` [Bug libfortran/50105] Possibly: " burnus at gcc dot gnu.org 2011-08-19 6:54 ` [Bug libfortran/50105] [4.6/4.7 Regression] " burnus at gcc dot gnu.org 2011-08-19 11:17 ` burnus at gcc dot gnu.org 2011-08-19 18:17 ` burnus at gcc dot gnu.org 2011-08-22 6:07 ` jvdelisle at gcc dot gnu.org 2011-10-26 17:21 ` jakub at gcc dot gnu.org 2012-01-10 0:41 ` jvdelisle at gcc dot gnu.org 2012-01-10 8:46 ` burnus at gcc dot gnu.org 2012-01-10 19:33 ` jvdelisle at gcc dot gnu.org 2012-01-12 9:08 ` burnus at gcc dot gnu.org 2012-02-03 19:22 ` tkoenig at gcc dot gnu.org 2012-02-18 9:54 ` burnus at gcc dot gnu.org 2012-02-18 17:51 ` dominiq at lps dot ens.fr 2012-03-01 14:56 ` jakub at gcc dot gnu.org 2013-01-02 17:24 ` burnus at gcc dot gnu.org [this message] 2013-01-02 20:46 ` [Bug libfortran/50105] [4.6/4.7/4.8 " jvdelisle at gcc dot gnu.org 2013-01-02 21:40 ` anlauf at gmx dot de 2013-02-15 7:39 ` 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=bug-50105-4-43nd1YkT36@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).