public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/30869] Rejects pointer to integer as loop variable
Date: Tue, 20 Feb 2007 09:03:00 -0000 [thread overview]
Message-ID: <20070220090347.9639.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30869-6642@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from burnus at gcc dot gnu dot org 2007-02-20 09:03 -------
Error: Loop variable at (1) cannot have the POINTER attribute
C820 (R831) The do-variable shall be a named scalar variable of type integer.
The program is accepted by ifort, NAG f95, g95 and sunf95.
--
burnus at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu dot
| |org
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Keywords| |rejects-valid
Last reconfirmed|0000-00-00 00:00:00 |2007-02-20 09:03:46
date| |
Summary|incorrect error message for |Rejects pointer to integer
|valid code |as loop variable
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30869
next prev parent reply other threads:[~2007-02-20 9:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 7:49 [Bug fortran/30869] New: incorrect error message for valid code jv244 at cam dot ac dot uk
2007-02-20 9:03 ` burnus at gcc dot gnu dot org [this message]
2007-02-20 20:32 ` [Bug fortran/30869] Rejects pointer to integer as loop variable tkoenig at gcc dot gnu dot org
2007-02-20 20:55 ` patchapp at dberlin dot org
2007-02-20 21:50 ` tkoenig at gcc dot gnu dot org
2007-02-28 21:37 ` [Bug fortran/30869] [4.1, 4.2 only] " tkoenig at gcc dot gnu dot org
2007-02-28 21:38 ` [Bug fortran/30869] [4.1 " tkoenig 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=20070220090347.9639.qmail@sourceware.org \
--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: link
Be 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).