This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [Patch, fortran] PR40011 - Problems with -fwhole-file

From: Thomas Koenig <tkoenig at netcologne dot de>
To: Richard Guenther <richard dot guenther at gmail dot com>
Cc: fortran at gcc dot gnu dot org, gcc-patches <gcc-patches at gcc dot gnu dot org>
Date: Tue, 25 May 2010 07:51:33 +0200
Subject: Re: [Patch, fortran] PR40011 - Problems with -fwhole-file
References: <AANLkTimVJfzHj3R9QpDgNctL402JHT5Pet3En_yp9Clm@mail.gmail.com> <1274734351.4414.4.camel@linux-fd1f.site> <AANLkTikRJmlAhwJ8RER_fFVkgmoeC2L4kV0RNWGEi4_k@mail.gmail.com>

Richard Guenther wrote:

> I can't see a single reason for -fno-whole-file as a way to change
> what the Fortran frontend presents to the middle-end 

The problem I see for some test cases is that -fwhole-file enables
(better) inlining, which can lead to tests being optimized away /
performed at run-time.  This could reduce testsuite coverage.

Follow-Ups:
- Re: [Patch, fortran] PR40011 - Problems with -fwhole-file
  - From: Richard Guenther

References:
- [Patch, fortran] PR40011 - Problems with -fwhole-file
  - From: Paul Richard Thomas
- Re: [Patch, fortran] PR40011 - Problems with -fwhole-file
  - From: Thomas Koenig
- Re: [Patch, fortran] PR40011 - Problems with -fwhole-file
  - From: Richard Guenther

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]