Re: [gfortran] fortran preprocessing, round 2

2005-11-02 Thread Richard Henderson
On Wed, Nov 02, 2005 at 12:20:36PM +0100, François-Xavier Coudert wrote: > I'll commit when 4.1 unfreezes before branching. Could that apply to > branch 4.0 as well? As you like. r~

Re: [gfortran] fortran preprocessing, round 2

2005-11-02 Thread François-Xavier Coudert
>> PR fortran/18452 >> * gcc/c.opt: Add a -lang-fortran option. >> * gcc/c-opts.c: Add a lang_fortran flag. >> (c_common_init_options): Handling the -lang-fortran option. >> (c_common_handle_option): Add a case for Fortran options in >> preprocessing. Remove case

Re: [gfortran] fortran preprocessing, round 2

2005-11-01 Thread Richard Henderson
On Tue, Nov 01, 2005 at 11:23:08PM +0100, FX Coudert wrote: > PR fortran/18452 > * gcc/c.opt: Add a -lang-fortran option. > * gcc/c-opts.c: Add a lang_fortran flag. > (c_common_init_options): Handling the -lang-fortran option. > (c_common_handle_option): Add a case for

Re: [gfortran] fortran preprocessing, round 2

2005-11-01 Thread Andrew Pinski
> This is an updated version of my patch taking care of warnings when cc1 > is called from gfortran to preprocess fortran source. I used a > different (and in my view, cleaner) approach: Fortran options are not > marked as C, but when preprocessing fortran source, cc1 is given a > -lang-fortran

[gfortran] fortran preprocessing, round 2

2005-11-01 Thread FX Coudert
This is an updated version of my patch taking care of warnings when cc1 is called from gfortran to preprocess fortran source. I used a different (and in my view, cleaner) approach: Fortran options are not marked as C, but when preprocessing fortran source, cc1 is given a -lang-fortran flag, whi