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 libfortran/114304] libgfortran I/O – bogus "Semicolon not allowed as separator with DECIMAL='point'" Date: Wed, 13 Mar 2024 19:32:44 +0000 [thread overview] Message-ID: <bug-114304-4-H8fbKXUp8z@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 #17 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> --- (In reply to Jeffrey A. Law from comment #16) > Per c#12, c#13, c#14 & c#15, dropping the regression marker, but leaving > open. Interestingly, the remaining part of this bug is also a regression, it just does not break LAPACK. Reverting this change fixes it which means the new test for pr105473 will fail. I have an idea where to put this check in read_complex() but I have not finished this and tested it. Jeffrey, if you would like me to push this, let me know. We can mark pr105473.f90 in the test suite to XFAIL or comment out the one check there that fails. diff --git a/libgfortran/io/list_read.c b/libgfortran/io/list_read.c index fb3f7dbc34d..c178acd61a5 100644 --- a/libgfortran/io/list_read.c +++ b/libgfortran/io/list_read.c @@ -471,8 +471,6 @@ eat_separator (st_parameter_dt *dtp) case ',': if (dtp->u.p.current_unit->decimal_status == DECIMAL_COMMA) { - generate_error (&dtp->common, LIBERROR_READ_VALUE, - "Comma not allowed as separator with DECIMAL='comma'"); unget_char (dtp, c); break; }
next prev parent reply other threads:[~2024-03-13 19:32 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 [this message] 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 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-H8fbKXUp8z@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).