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
New version of the patch attached (this time), to answer Joseph's
remark. Original questions still apply, including:
What should "gfortran -fdollar-ok a.f b.c" do, if -fdollar-ok if a
fortran-only option?
FX
2005-10-31 Francois-Xavier Coudert <[EMAIL PROTECTED]>
PR fortran/18452
On Mon, Oct 31, 2005 at 01:20:48PM +0100, FX Coudert wrote:
> New version of the patch attached, to answer Joseph's remark.
Actually, no :-)
> 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.
On Mon, Oct 31, 2005 at 12:51:40AM +0100, FX Coudert wrote:
>This is a patch proposal about PR fortran/18452. In short, to preprocess
>fortran source files, gfortran calls cc1 with its own options, which
>gives warnings like:
>
>$ gfortran -fdollar-ok a.F90
>cc1: warning: command line option "-fd
New version of the patch attached, to answer Joseph's remark. Original
questions still apply, including:
What should "gfortran -fdollar-ok a.f b.c" do, if -fdollar-ok if a
fortran-only option?
FX
On Mon, 31 Oct 2005, FX Coudert wrote:
> * gcc/c-opts.c: Add cases for all Fortran options declared as C
> and used only when preprocessing.
Someone building without Fortran (whether with it disabled, or without it
in the source tree) won't get the enumerators from fortran/lang.o
This is a patch proposal about PR fortran/18452. In short, to preprocess
fortran source files, gfortran calls cc1 with its own options, which
gives warnings like:
$ gfortran -fdollar-ok a.F90
cc1: warning: command line option "-fdollar-ok" is valid for F95 but not
for C
A few (two exactly) o
