From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21257 invoked by alias); 9 Dec 2009 11:52:52 -0000 Received: (qmail 21195 invoked by alias); 9 Dec 2009 11:52:41 -0000 Date: Wed, 09 Dec 2009 11:52:00 -0000 Message-ID: <20091209115241.21194.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/40011] Problems with -fwhole-file In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "rguenther at suse dot de" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-12/txt/msg00939.txt.bz2 ------- Comment #52 from rguenther at suse dot de 2009-12-09 11:52 ------- Subject: Re: Problems with -fwhole-file On Wed, 9 Dec 2009, jv244 at cam dot ac dot uk wrote: > ------- Comment #51 from jv244 at cam dot ac dot uk 2009-12-09 11:50 ------- > still failing with current trunk, also leading to miscomples (see PR38913). As > a consequence, should one disable -fwhole-file (and consequently -flto) for > Fortran before release? As neither is enabled by default I instead recommend to document the experimental status instead. Note that -flto works around most of the frontend issues by performing its own type and decl unification. Richard. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40011