public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paulthomas2 at wanadoo dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/17917] gfortran ICE on "equivalence"
Date: Wed, 03 Aug 2005 07:54:00 -0000	[thread overview]
Message-ID: <20050803075422.12039.qmail@sourceware.org> (raw)
In-Reply-To: <20041009232408.17917.olchansk@panix.com>


------- Additional Comments From paulthomas2 at wanadoo dot fr  2005-08-03 07:54 -------
(In reply to comment #11)
> Patch posted here: http://gcc.gnu.org/ml/fortran/2005-06/msg00307.html

This is still not complete.  The example below produces separate unions, which 
represent the equivalences, in sub1 and sub2.  They need to be promoted to a 
more elevated namespace AND declared external, so that loaded procedures also 
pick up the same union.  The COMMON code is mostly OK, so I will be applying 
that to module equivalences.  I'm on to it, as promised on the list.....

Paul T

module equiv
  real       ::  x(10), y(2)
  equivalence (y(1), x(5))
end module equiv

subroutine sub1 ()
  use equiv
  x =(/(real (i), i = 1,10)/)
end subroutine sub1

subroutine sub2 ()
  use equiv
  print *, y
end subroutine sub2

program test_equiv
  call sub1 ()
  call sub2 ()
end program test_equiv



-- 


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


  parent reply	other threads:[~2005-08-03  7:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-09 23:24 [Bug fortran/17917] New: " olchansk at panix dot com
2004-10-10 15:45 ` [Bug fortran/17917] " pinskia at gcc dot gnu dot org
2004-10-10 16:54 ` tobi at gcc dot gnu dot org
2004-10-10 17:45 ` tobi at gcc dot gnu dot org
2004-10-11 16:37 ` tobi at gcc dot gnu dot org
2004-12-18 11:37 ` paulthomas2 at wanadoo dot fr
2005-01-10 13:40 ` aj at gcc dot gnu dot org
2005-03-12  0:15 ` tobi at gcc dot gnu dot org
2005-04-03 18:11 ` tcallawa at redhat dot com
2005-04-12 18:33 ` koziol at ncsa dot uiuc dot edu
2005-05-06 22:49 ` pinskia at gcc dot gnu dot org
2005-06-16 16:38 ` tobi at gcc dot gnu dot org
2005-08-03  7:54 ` paulthomas2 at wanadoo dot fr [this message]
2005-08-30 19:14 ` pinskia at gcc dot gnu dot org
2005-09-03 12:05 ` pinskia at gcc dot gnu dot org
2005-09-09  0:25 ` cvs-commit at gcc dot gnu dot org
2005-09-09  9:07 ` cvs-commit at gcc dot gnu dot org
2005-09-09 22:15 ` 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=20050803075422.12039.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).