public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/107237] Error: non-constant array in DATA statement (1) Date: Wed, 12 Oct 2022 15:45:03 +0000 [thread overview] Message-ID: <bug-107237-4-OyAXlh5gsn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107237-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107237 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID CC| |anlauf at gcc dot gnu.org Status|UNCONFIRMED |RESOLVED --- Comment #1 from anlauf at gcc dot gnu.org --- It would help if you chose a font that can distinguish 'l' (ell) from '1' (one). Adding "implicit none" of -fimplicit-none tells you: 2 | DATA A(l), A(2), A(3), A(4) /0.0, 0.0, 0.0, 0.0/ | 1 Error: Symbol 'l' at (1) has no IMPLICIT type
next prev parent reply other threads:[~2022-10-12 15:45 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-12 14:18 [Bug fortran/107237] New: " ptw at tpointsw dot uk 2022-10-12 15:45 ` anlauf at gcc dot gnu.org [this message] 2022-10-12 16:18 ` [Bug fortran/107237] " ptw at tpointsw dot uk
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-107237-4-OyAXlh5gsn@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).