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/114304] [13/14 Regression] libgfortran I/O – bogus "Semicolon not allowed as separator with DECIMAL='point'" Date: Mon, 08 Apr 2024 08:38:31 +0000 [thread overview] Message-ID: <bug-114304-4-BSrN5TozkL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114304-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114304 --- Comment #28 from Tobias Burnus <burnus at gcc dot gnu.org> --- Created attachment 57896 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57896&action=edit Testcase It seems as if 'tabs' cause problems, e.g. for: profile_single_file = .true. where there are two tabs before '='. * * * The problem seems to be that the new code uses: - eat_spaces (dtp); dtp->u.p.comma_flag = 0; + c = next_char (dtp); + if (c == ' ') + { + eat_spaces (dtp); Thus, it explicitly checks for ' ' while eat_spaces handles: while (c != EOF && (c == ' ' || c == '\r' || c == '\t')); Testcase attached. I think we need at least an "|| c == '\t'"; I guess '\r' isn't really required here, or is it?
next prev parent reply other threads:[~2024-04-08 8:38 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-11 11:40 [Bug libfortran/114304] New: [14 Regression] Rejects lapack test rguenth at gcc dot gnu.org 2024-03-11 11:42 ` [Bug libfortran/114304] " rguenth at gcc dot gnu.org 2024-03-11 11:52 ` rguenth at gcc dot gnu.org 2024-03-11 12:26 ` burnus at gcc dot gnu.org 2024-03-11 12:31 ` burnus at gcc dot gnu.org 2024-03-11 12:51 ` [Bug libfortran/114304] [14 Regression] libgfortran I/O – bogus "Semicolon not allowed as separator with DECIMAL='point'" burnus at gcc dot gnu.org 2024-03-11 16:41 ` burnus at gcc dot gnu.org 2024-03-11 17:27 ` [Bug libfortran/114304] [13/14 " jvdelisle at gcc dot gnu.org 2024-03-11 18:18 ` jvdelisle at gcc dot gnu.org 2024-03-11 19:03 ` jvdelisle at gcc dot gnu.org 2024-03-11 19:13 ` rguenther at suse dot de 2024-03-11 21:12 ` jvdelisle at gcc dot gnu.org 2024-03-11 22:24 ` cvs-commit at gcc dot gnu.org 2024-03-11 22:45 ` cvs-commit at gcc dot gnu.org 2024-03-12 8:52 ` burnus at gcc dot gnu.org 2024-03-12 16:42 ` jvdelisle at gcc dot gnu.org 2024-03-13 13:39 ` [Bug libfortran/114304] " law at gcc dot gnu.org 2024-03-13 19:32 ` jvdelisle at gcc dot gnu.org 2024-03-14 3:02 ` law at gcc dot gnu.org 2024-03-14 9:26 ` [Bug libfortran/114304] [13/14 Regression] " burnus at gcc dot gnu.org 2024-03-14 15:56 ` jvdelisle at gcc dot gnu.org 2024-03-15 15:00 ` law at gcc dot gnu.org 2024-03-15 23:51 ` jvdelisle at gcc dot gnu.org 2024-04-06 13:56 ` cvs-commit at gcc dot gnu.org 2024-04-08 6:03 ` chenglulu at loongson dot cn 2024-04-08 7:24 ` rguenth at gcc dot gnu.org 2024-04-08 7:49 ` rguenth at gcc dot gnu.org 2024-04-08 8:06 ` rguenth at gcc dot gnu.org 2024-04-08 8:09 ` rguenth at gcc dot gnu.org 2024-04-08 8:38 ` burnus at gcc dot gnu.org [this message] 2024-04-08 9:36 ` rguenther at suse dot de 2024-04-08 10:00 ` burnus at gcc dot gnu.org 2024-04-08 19:48 ` cvs-commit at gcc dot gnu.org 2024-04-08 20:07 ` jvdelisle at gcc dot gnu.org 2024-04-08 20:15 ` jvdelisle at gcc dot gnu.org 2024-04-22 4:23 ` cvs-commit at gcc dot gnu.org 2024-04-22 4:29 ` 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-114304-4-BSrN5TozkL@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).