From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-347849-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 1691 invoked by alias); 20 Feb 2011 11:40:13 -0000
Received: (qmail 1678 invoked by uid 22791); 20 Feb 2011 11:40:12 -0000
X-SWARE-Spam-Status: No, hits=-2.9 required=5.0	tests=ALL_TRUSTED,BAYES_00
X-Spam-Check-By: sourceware.org
Received: from localhost (HELO gcc.gnu.org) (127.0.0.1)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 20 Feb 2011 11:40:08 +0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45077] ICE with -fwhole-file in fold_convert_loc, at fold-const.c:2021
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-45077-4-BWOg72WqA2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-45077-4@http.gcc.gnu.org/bugzilla/>
References: <bug-45077-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Date: Sun, 20 Feb 2011 14:18:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2011-02/txt/msg02315.txt.bz2

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

--- Comment #7 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-02-20 11:39:56 UTC ---
(In reply to comment #6)
> Fixes the problem.  Bootstraps and regtests OK.

I glanced at it and it looks OK.

> dg-additional-sources is not sufficient is it?  That is does it generate:
> gfortran source1.f90 source2.f90
> or 
> gfortran -c source1.f90 -o source1.o
> gfortran source2.f90 source1.0

I think both are effectively the same: For "gfortran source2.f90 source1.f90",
the driver (gfortran) calls twice the compiler (f951) which generates in
/tmp/... the assembler files, the driver then calls the assembler (as) twice
and, finally, the linker (collect1). The driver only combined the two source
files when "-combined" is used, though I think that feature was not available
for Fortran and will not work with dg-additional-sources.
That can be seen when running "gfortran -v source2.f90 source1.f90" by looking
for the f951 lines.

Note: The file specified by dg-additional-sources is compiled after the one
which has the "dg-additional-sources" specified. Additionally, one needs to
provide a fall-back compilation as the second file is also compiled
independently.
See pr37287-1.f90 and pr37287-2.F90 as an example.