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: Sat, 18 Dec 2004 11:37:00 -0000 [thread overview]
Message-ID: <20041218113704.29097.qmail@sourceware.org> (raw)
In-Reply-To: <20041009232408.17917.olchansk@panix.com>
------- Additional Comments From paulthomas2 at wanadoo dot fr 2004-12-18 11:37 -------
(In reply to comment #1)
> Confirmed.
Note that this bug is provoked by this minimalist version of the above
module test_equiv !Bug 17917
real a(2),b(4)
equivalence (a(1),b(3))
end module test_equiv
However, equivalence does what it should in programs, subroutines and
functions. For example, this works correctly:
PROGRAM test_equiv ! .not.Bug 17917
common b
real a(2)
INTEGER b(4)
equivalence (a(1),b(3))
b=(/1,2,3,4/)
PRINT *,a
end PROGRAM test_equiv
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17917
next prev parent reply other threads:[~2004-12-18 11:37 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 [this message]
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
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=20041218113704.29097.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).