This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran 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: [gfortran] gfortran options and cc1 warnings

From: FX Coudert <fxcoudert at gmail dot com>
To: Thomas Koenig <Thomas dot Koenig at online dot de>
Cc: "Joseph S. Myers" <joseph at codesourcery dot com>, gfortran <fortran at gcc dot gnu dot org>,patch <gcc-patches at gcc dot gnu dot org>, GCC Development <gcc at gcc dot gnu dot org>
Date: Mon, 31 Oct 2005 18:54:38 +0100
Subject: Re: [gfortran] gfortran options and cc1 warnings
References: <43655C8C.20403@gmail.com> <Pine.LNX.4.64.0510310005070.11664@digraph.polyomino.org.uk> <43660C20.2010103@gmail.com> <20051031173334.GA5460@meiner.onlinehome.de>

What should "gfortran -fdollar-ok a.f b.c" do, if -fdollar-ok if a fortran-only option?
It shouldn't pass -fdollar-ok to cc1, IMHO.

I'm not sure about how other languages handle that. Trying to mix java and C gives:

$ gcj -c Example.java a.c -Wredundant-modifiers cc1: warning: command line option "-Wredundant-modifiers" is valid for Java but not for C

So, I guess we need to align on that...

FX

References:
- [gfortran] gfortran options and cc1 warnings
  - From: FX Coudert
- Re: [gfortran] gfortran options and cc1 warnings
  - From: Joseph S. Myers
- Re: [gfortran] gfortran options and cc1 warnings
  - From: FX Coudert
- Re: [gfortran] gfortran options and cc1 warnings
  - From: Thomas Koenig

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