public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jv244 at cam dot ac dot uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/25101] New: better diagnostic needed Date: Sat, 26 Nov 2005 18:08:00 -0000 [thread overview] Message-ID: <bug-25101-6642@http.gcc.gnu.org/bugzilla/> (raw) using GNU Fortran 95 (GCC) 4.1.0 20051126 (prerelease) with '-g -pedantic -std=f95', I get a bad / no diagnostic for the following invalid code: INTEGER :: A(10),J(2),I FORALL(I=1:2:0) A(I)=1 END FORALL END -- Summary: better diagnostic needed Product: gcc Version: 4.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jv244 at cam dot ac dot uk http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25101
next reply other threads:[~2005-11-26 18:08 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-11-26 18:08 jv244 at cam dot ac dot uk [this message] 2005-11-27 3:56 ` [Bug fortran/25101] " kargl at gcc dot gnu dot org 2005-11-30 13:38 ` [Bug fortran/25101] Zero stride allowed in FORALL:s eedelman at gcc dot gnu dot org 2006-01-02 23:38 ` kargl at gcc dot gnu dot org 2006-01-03 22:01 ` kargl at gcc dot gnu dot org 2006-01-03 22:02 ` [Bug fortran/25101] [4.1] " kargl at gcc dot gnu dot org 2006-01-06 20:04 ` kargl at gcc dot gnu dot org 2006-01-06 20:07 ` kargl at gcc dot gnu dot 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-25101-6642@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).