public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nmm1 at cam dot ac.uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/54679] Erroneous "Expected P edit descriptor" in conjunction with L descriptor Date: Sun, 23 Sep 2012 12:19:00 -0000 [thread overview] Message-ID: <bug-54679-4-Baekg6CJYJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54679-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54679 --- Comment #1 from Nick Maclaren <nmm1 at cam dot ac.uk> 2012-09-23 12:19:00 UTC --- Please reduce the severity to trivial, and change it to "Confusing diagnostic"! It's my error, at root, but gfortran could do better. I had forgotten the relevant constraint (C1006 in Fortran 2003). However, the syntax rule R1005 on the same page specifies that a width is mandatory for the L descriptor, so the actual error is that a width of zero is erroneous.
next prev parent reply other threads:[~2012-09-23 12:19 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-23 12:04 [Bug fortran/54679] New: " nmm1 at cam dot ac.uk 2012-09-23 12:19 ` nmm1 at cam dot ac.uk [this message] 2012-09-23 16:24 ` [Bug fortran/54679] " kargl at gcc dot gnu.org 2013-06-27 9:21 ` dominiq at lps dot ens.fr
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-54679-4-Baekg6CJYJ@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).