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/18833] ICE 'missing spec' on integer/char equivalence
Date: Fri, 22 Jul 2005 14:07:00 -0000	[thread overview]
Message-ID: <20050722140109.10332.qmail@sourceware.org> (raw)
In-Reply-To: <20041204203017.18833.Thomas.Koenig@online.de>


------- Additional Comments From Tobias dot Schlueter at physik dot uni-muenchen dot de  2005-07-22 14:01 -------
Subject: Re:  ICE 'missing spec' on integer/char equivalence

federico dot carminati at cern dot ch wrote:
>    this is valid f90/95 code. Equivalence cannot  contain sym%val as  
> far as I understand, but they can cointain derived types as long as
> they are sequenced.

I'm not sure if oyu meant to say the right thing, so let me clarify: sym%name
and sym are allowed if sym is of a type with the sequence attribute.

I haven't yet looked over the posted program.


-- 


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


  parent reply	other threads:[~2005-07-22 14:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-04 20:30 [Bug fortran/18833] New: " Thomas dot Koenig at online dot de
2004-12-05 15:35 ` [Bug fortran/18833] " pinskia at gcc dot gnu dot org
2004-12-05 20:59 ` tobi at gcc dot gnu dot org
2005-04-08 12:20 ` pinskia at gcc dot gnu dot org
2005-04-08 12:23 ` pinskia at gcc dot gnu dot org
2005-07-22 12:44 ` jakub at redhat dot com
2005-07-22 14:01 ` federico dot carminati at cern dot ch
2005-07-22 14:07 ` Tobias dot Schlueter at physik dot uni-muenchen dot de [this message]
2005-07-22 15:31 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2005-08-06 10:01 ` cvs-commit at gcc dot gnu dot org
2005-08-06 10:13 ` cvs-commit at gcc dot gnu dot org
2005-08-06 13:35 ` pinskia 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=20050722140109.10332.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).