This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [Patch, fortran] PR40011 - Problems with -fwhole-file
- From: Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- To: Paul Richard Thomas <paul dot richard dot thomas at gmail dot com>
- Cc: fortran at gcc dot gnu dot org, gcc-patches <gcc-patches at gcc dot gnu dot org>
- Date: Mon, 24 May 2010 13:28:53 -0700
- Subject: Re: [Patch, fortran] PR40011 - Problems with -fwhole-file
- References: <AANLkTimVJfzHj3R9QpDgNctL402JHT5Pet3En_yp9Clm@mail.gmail.com>
On Mon, May 24, 2010 at 10:10:16PM +0200, Paul Richard Thomas wrote:
> The attached patch fixes the testcase of comment #42 of the above PR.
> I feel somewhat embarrassed about the fault because it is a rather
> trivial error in one of my earlier patches. The patch and the
> ChangeLogs are self-explanatory.
>
> I would now like proposals about how to introduce -fwhole-file as the default:
>
> (i) A -fno-whole-file or would std=legacy as an over-ride?
> (ii) Modify some of the testcases by fixing their problems and using
> -fno-whole-file or std=legacy for the rest - or the latter for all of
> them?
>
I strongly prefer -fno-whole-file over -std=legacy.
If you make -fwhole-file the default, then I would
want an option that allows me to disable the
default and still use -std=f2003. In fact, I don't
even understand what -f[no-]whole-file has do with
legacy Fortran features.
--
Steve