From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29127 invoked by alias); 18 Dec 2004 11:37:11 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 29098 invoked by uid 48); 18 Dec 2004 11:37:04 -0000 Date: Sat, 18 Dec 2004 11:37:00 -0000 Message-ID: <20041218113704.29097.qmail@sourceware.org> From: "paulthomas2 at wanadoo dot fr" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20041009232408.17917.olchansk@panix.com> References: <20041009232408.17917.olchansk@panix.com> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug fortran/17917] gfortran ICE on "equivalence" X-Bugzilla-Reason: CC X-SW-Source: 2004-12/txt/msg02632.txt.bz2 List-Id: ------- 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