public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Tobias dot Schlueter at physik dot uni-muenchen dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/20900] use-associated variable may not be equivalenced
Date: Thu, 19 May 2005 19:37:00 -0000 [thread overview]
Message-ID: <20050519192247.16729.qmail@sourceware.org> (raw)
In-Reply-To: <20050408160549.20900.jv244@cam.ac.uk>
------- Additional Comments From Tobias dot Schlueter at physik dot uni-muenchen dot de 2005-05-19 19:22 -------
Subject: Re: use-associated variable may not be equivalenced
jv244 at cam dot ac dot uk wrote:
> ------- Additional Comments From jv244 at cam dot ac dot uk 2005-05-19 17:54 -------
> (In reply to comment #1)
>
>>There's no 11.7 neither in the F95 nor the F2K drafts I'm having. This is
>>invalid by the constraints in 5.5.1 in the F95 draft. Is there any other
>>constraint you were aiming at?
>
>
> No, off-by-one, refering to 'note 11.8' in 11.3.2 which mentions the same
> constraint.
Thanks, I had only checked note 11.7 :-)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20900
next prev parent reply other threads:[~2005-05-19 19:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 16:06 [Bug fortran/20900] New: error needed jv244 at cam dot ac dot uk
2005-05-19 18:03 ` [Bug fortran/20900] use-associated variable may not be equivalenced tobi at gcc dot gnu dot org
2005-05-19 18:49 ` jv244 at cam dot ac dot uk
2005-05-19 19:37 ` Tobias dot Schlueter at physik dot uni-muenchen dot de [this message]
2005-09-26 19:33 ` pault at gcc dot gnu dot org
2005-10-01 7:40 ` cvs-commit at gcc dot gnu dot org
2005-10-01 15:57 ` pinskia at gcc dot gnu dot org
[not found] <bug-20900-6642@http.gcc.gnu.org/bugzilla/>
2005-10-12 5:43 ` cvs-commit 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=20050519192247.16729.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).