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/98686] Namelist group objects shall be defined before appearing in namelist for -std=f2018 Date: Sun, 14 Feb 2021 01:53:36 +0000 [thread overview] Message-ID: <bug-98686-4-Npdmi578cS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98686-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98686 Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |jvdelisle at gcc dot gnu.org Status|NEW |ASSIGNED CC| |jvdelisle at gcc dot gnu.org --- Comment #2 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> --- I have this working: pr98686.f90:2:19: 2 | namelist /NML/ x, m, q | 1 Error: Symbol ‘x’ in namelist ‘nml’ at (1) must be defined before the namelist is declared. Does this read OK?
next prev parent reply other threads:[~2021-02-14 1:53 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-14 17:10 [Bug fortran/98686] New: " anlauf at gcc dot gnu.org 2021-01-14 17:11 ` [Bug fortran/98686] " anlauf at gcc dot gnu.org 2021-01-14 18:05 ` anlauf at gcc dot gnu.org 2021-01-19 9:53 ` dominiq at lps dot ens.fr 2021-02-14 1:53 ` jvdelisle at gcc dot gnu.org [this message] 2021-02-14 2:43 ` jvdelisle at gcc dot gnu.org 2021-02-14 19:27 ` jvdelisle at gcc dot gnu.org 2021-02-15 20:17 ` jvdelisle at gcc dot gnu.org 2021-02-19 20:48 ` cvs-commit at gcc dot gnu.org 2021-02-22 4:27 ` 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-98686-4-Npdmi578cS@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).