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/105473] semicolon allowed when list-directed read integer with decimal='point'
Date: Wed, 03 Apr 2024 03:36:04 +0000	[thread overview]
Message-ID: <bug-105473-4-9hZzSirheU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105473-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105473

--- Comment #36 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Created attachment 57854
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57854&action=edit
Modified extended test case

I modified the extended test case so I could review this and summarize.
Currently this is what we get with my comments at the end of each line. I
marked some that I think are clearly incorrect.  Maybe OK depends on on
strictly one chooses to interpret what the standard says.  If we assume that
one or more spaces is an acceptable separator if followed by a non-value I
indicate those with the word space.

comma, isreal = F, testinput =      ; n=     42 ios=    0  OK, null read
point, isreal = F, testinput =      ; n=     42 ios=    0  maybe OK
comma, isreal = F, testinput =      , n=     42 ios= 5010  OK, error
point, isreal = F, testinput =      , n=     42 ios=    0  OK, null read
comma, isreal = F, testinput =      . n=     42 ios= 5010  OK, error
point, isreal = F, testinput =      . n=     42 ios= 5010  OK, error
comma, isreal = F, testinput =     5. n=     42 ios= 5010  OK, error
point, isreal = F, testinput =     5. n=     42 ios= 5010  OK, error
comma, isreal = F, testinput =     5, n=     42 ios= 5010  OK, error
point, isreal = F, testinput =     5, n=      5 ios=    0  OK, good read
comma, isreal = F, testinput =     5; n=      5 ios=    0  OK, good read
point, isreal = F, testinput =     5; n=      5 ios=    0  maybe OK
comma, isreal = F, testinput =    7 . n=      7 ios=    0  OK, good read space
point, isreal = F, testinput =    7 . n=      7 ios=    0  OK, good read space
comma, isreal = F, testinput =    7 , n=     42 ios= 5010  Incorrect
point, isreal = F, testinput =    7 , n=      7 ios=    0  OK, good read
comma, isreal = F, testinput =    7 ; n=      7 ios=    0  OK, good read space
point, isreal = F, testinput =    7 ; n=      7 ios=    0  OK, good read space
comma, isreal = T, testinput =     8. r=  42.00 ios= 5010  OK, error
point, isreal = T, testinput =     8. r=   8.00 ios=    0  OK, good read
comma, isreal = T, testinput =     8, r=   8.00 ios=    0  OK, good read
point, isreal = T, testinput =     8, r=   8.00 ios=    0  OK, good read
comma, isreal = T, testinput =     8; r=   8.00 ios=    0  OK, good read
point, isreal = T, testinput =     8; r=   8.00 ios=    0  maybe OK
comma, isreal = T, testinput =    9 . r=   9.00 ios=    0  OK, good read space
point, isreal = T, testinput =    9 . r=   9.00 ios=    0  OK, good read space
comma, isreal = T, testinput =    9 , r=   9.00 ios= 5010  Incorrect, space?
point, isreal = T, testinput =    9 , r=   9.00 ios=    0  OK, good read
comma, isreal = T, testinput =    9 ; r=   9.00 ios=    0  OK, good read
point, isreal = T, testinput =    9 ; r=   9.00 ios=    0  maybe OK
comma, isreal = T, testinput =   3,3. r=  42.00 ios= 5010  OK, error
point, isreal = T, testinput =   3.3. r=  42.00 ios= 5010  OK, error
comma, isreal = T, testinput =   3,3, r=  42.00 ios= 5010  OK, error
comma, isreal = T, testinput =   3,3; r=   3.30 ios=    0  OK, good read
point, isreal = T, testinput =   3.3; r=   3.30 ios=    0  maybe OK
comma, isreal = T, testinput =  4,4 . r=   4.40 ios=    0  OK, good read space
point, isreal = T, testinput =  4.4 . r=   4.40 ios=    0  OK, goor read space
comma, isreal = T, testinput =  4,4 , r=   4.40 ios= 5010  Incorrect, space?
point, isreal = T, testinput =  4.4 , r=   4.40 ios=    0  OK, good read
comma, isreal = T, testinput =  4,4 ; r=   4.40 ios=    0  OK, good read
point, isreal = T, testinput =  4.4 ; r=   4.40 ios=    0  OK, good read space

I have a followup comment on this.

  parent reply	other threads:[~2024-04-03  3:36 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04  8:38 [Bug fortran/105473] New: " john.harper at vuw dot ac.nz
2022-05-05  2:14 ` [Bug fortran/105473] " jvdelisle2 at gmail dot com
2022-05-05  2:21 ` jvdelisle2 at gmail dot com
2022-05-05  2:50 ` harper at msor dot vuw.ac.nz
2022-05-06  1:26 ` jvdelisle2 at gmail dot com
2022-05-06 20:39 ` anlauf at gcc dot gnu.org
2022-05-08 14:54 ` jvdelisle at gcc dot gnu.org
2022-05-14 22:00 ` jvdelisle at gcc dot gnu.org
2022-05-15  8:59 ` harper at msor dot vuw.ac.nz
2022-05-15 14:37 ` jvdelisle at gcc dot gnu.org
2022-05-15 15:56 ` jvdelisle at gcc dot gnu.org
2022-05-16  0:10 ` harper at msor dot vuw.ac.nz
2022-05-16  0:42 ` jvdelisle at gcc dot gnu.org
2022-05-16  0:49 ` jvdelisle at gcc dot gnu.org
2022-05-16  0:55 ` jvdelisle at gcc dot gnu.org
2022-05-16  1:44 ` harper at msor dot vuw.ac.nz
2022-05-16  4:12 ` harper at msor dot vuw.ac.nz
2022-05-16 21:13 ` harper at msor dot vuw.ac.nz
2022-05-18  2:52 ` jvdelisle at gcc dot gnu.org
2022-05-19  0:10 ` harper at msor dot vuw.ac.nz
2022-06-03  4:33 ` jvdelisle at gcc dot gnu.org
2022-06-03  9:11 ` harper at msor dot vuw.ac.nz
2022-06-03 21:04 ` jvdelisle at gcc dot gnu.org
2022-06-04  3:47 ` harper at msor dot vuw.ac.nz
2022-07-02 17:14 ` jvdelisle at gcc dot gnu.org
2022-07-03  3:52 ` harper at msor dot vuw.ac.nz
2022-07-04  3:48 ` jvdelisle at gcc dot gnu.org
2024-02-17 18:04 ` cvs-commit at gcc dot gnu.org
2024-03-08  0:29 ` cvs-commit at gcc dot gnu.org
2024-03-08  0:30 ` jvdelisle at gcc dot gnu.org
2024-03-08  7:21 ` john.harper at vuw dot ac.nz
2024-03-09 19:12 ` jvdelisle at gcc dot gnu.org
2024-03-11 12:48 ` burnus at gcc dot gnu.org
2024-03-11 22:48 ` jvdelisle at gcc dot gnu.org
2024-03-14  8:40 ` burnus at gcc dot gnu.org
2024-03-14  9:16 ` burnus at gcc dot gnu.org
2024-04-03  3:36 ` jvdelisle at gcc dot gnu.org [this message]
2024-04-03  3:50 ` jvdelisle at gcc dot gnu.org
2024-04-06 13:56 ` cvs-commit at gcc dot gnu.org
2024-04-22  4:23 ` cvs-commit at gcc dot gnu.org
2024-04-22  4:25 ` jvdelisle 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-105473-4-9hZzSirheU@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).