public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35680] [4.3/4.4 regression] ICE on invalid transfer in variable declaration
Date: Wed, 17 Sep 2008 08:56:00 -0000	[thread overview]
Message-ID: <20080917085513.1854.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35680-10259@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from pault at gcc dot gnu dot org  2008-09-17 08:55 -------
(In reply to comment #4)
> 4.3.2 is released, changing milestones to 4.3.3.
> 
Although this passes Lahey with only a warning that the return value is not
set, it manifestly is standard defying according to 7.1.6.2

A variable in a specification expression shall have its type and type
parameters, if any, specified by a previous declaration in the same scoping
unit, or by the implicit typing rules in effect for the scoping unit, or by
host or use association. If a variable in a specification expression is typed
by
the implicit typing rules, its appearance in any subsequent type declaration
statement shall confirm the implied type and type parameters.

Inverting the order of the declarations should make the code legal.

Paul 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35680


  parent reply	other threads:[~2008-09-17  8:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24 18:45 [Bug fortran/35680] New: " fxcoudert at gcc dot gnu dot org
2008-03-25 20:46 ` [Bug fortran/35680] " pault at gcc dot gnu dot org
2008-03-25 23:18 ` burnus at gcc dot gnu dot org
2008-03-27 22:26 ` rguenth at gcc dot gnu dot org
2008-06-06 15:04 ` rguenth at gcc dot gnu dot org
2008-07-22 12:12 ` burnus at gcc dot gnu dot org
2008-08-27 22:08 ` jsm28 at gcc dot gnu dot org
2008-09-17  8:56 ` pault at gcc dot gnu dot org [this message]
2008-09-28 19:34 ` pault at gcc dot gnu dot org
2008-09-28 19:50 ` pault at gcc dot gnu dot org
2008-09-28 20:51 ` dominiq at lps dot ens dot fr
2008-09-29 20:26 ` dominiq at lps dot ens dot fr
2008-10-02 15:22 ` pault at gcc dot gnu dot org
2008-10-02 15:49 ` dominiq at lps dot ens dot fr
2008-10-03 12:14 ` pault at gcc dot gnu dot org
2008-10-03 22:24 ` dominiq at lps dot ens dot fr
2008-10-04 11:57 ` pault at gcc dot gnu dot org
2008-10-05 18:56 ` pault at gcc dot gnu dot org
2008-10-11 10:01 ` pault at gcc dot gnu dot org
2008-10-11 10:03 ` pault 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=20080917085513.1854.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).