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/109662] bad namelist input but gfortran accepted it Date: Thu, 04 May 2023 03:05:49 +0000 [thread overview] Message-ID: <bug-109662-4-IcxiTGqItq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109662-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109662 --- Comment #5 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> --- Is this acceptable: $ ./a.out Compiler version = GCC version 14.0.0 20230424 (experimental) Compiler options = -mtune=generic -march=x86-64 -Wpedantic -fpre-include=/usr/include/finclude/math-vector-fortran.h At line 9 of file pr109662.f90 Fortran runtime error: Comma after namelist name not allowed Should I allow it with -std=legacy?
next prev parent reply other threads:[~2023-05-04 3:05 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-28 8:20 [Bug fortran/109662] New: " john.harper at vuw dot ac.nz 2023-04-28 21:20 ` [Bug libfortran/109662] " anlauf at gcc dot gnu.org 2023-04-30 22:40 ` kargl at gcc dot gnu.org 2023-05-01 0:37 ` jvdelisle at gcc dot gnu.org 2023-05-01 3:05 ` jvdelisle at gcc dot gnu.org 2023-05-04 3:05 ` jvdelisle at gcc dot gnu.org [this message] 2023-05-04 4:59 ` john.harper at vuw dot ac.nz 2023-05-04 6:00 ` john.harper at vuw dot ac.nz 2023-05-05 2:44 ` jvdelisle at gcc dot gnu.org 2023-05-06 14:23 ` cvs-commit at gcc dot gnu.org 2023-05-06 14:45 ` jvdelisle at gcc dot gnu.org 2023-05-07 2:15 ` john.harper at vuw dot ac.nz 2023-05-07 18:14 ` jvdelisle at gcc dot gnu.org 2023-05-07 18:35 ` jvdelisle at gcc dot gnu.org 2023-05-07 21:46 ` john.harper at vuw dot ac.nz 2023-05-07 21:55 ` john.harper at vuw dot ac.nz 2023-05-07 22:10 ` john.harper at vuw dot ac.nz 2023-05-08 2:03 ` cvs-commit at gcc dot gnu.org 2023-05-09 0:41 ` jvdelisle at gcc dot gnu.org 2023-05-09 1:15 ` jvdelisle at gcc dot gnu.org 2023-05-12 20:41 ` cvs-commit at gcc dot gnu.org 2023-05-12 20:41 ` cvs-commit at gcc dot gnu.org 2023-08-25 1:03 ` 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-109662-4-IcxiTGqItq@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).