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: [Fortran, DRAFT patch] PR 46321 - [OOP] Polymorphic deallocation


Hi,

> By contrast, I assume that you (Janus) build GCC with the C compiler, i.e.
> you configure with --disable-build-poststage1-with-cxx.

actually I used --disable-bootstrap, which also has the effect that
gfortran is built with the C compiler.


> Thus, a default boot strap, ?shouldn't fail. Nonetheless, it is useful to
> keep compatibility with C and bootstrapping with
> --disable-build-poststage1-with-cxx.Hence, the warnings should be fixed.
> (Bootstrapping implies -Werror.)

Right. I'm not sure what the further plans are for GCC regarding the C
vs C++ issue, but as long as GCC can still be built with a C compiler,
one should probably avoid unnecessary C++isms.

Cheers,
Janus



>> /home/jweil/gcc48/trunk/gcc/fortran/class.c: In function
>> ‘gfc_find_derived_vtab’:
>> /home/jweil/gcc48/trunk/gcc/fortran/class.c:912:8: warning: ISO C90
>> forbids mixed declarations and code [-pedantic]
>> /home/jweil/gcc48/trunk/gcc/fortran/class.c:932:7: warning: C++ style
>> comments are not allowed in ISO C90 [enabled by default]
>> /home/jweil/gcc48/trunk/gcc/fortran/class.c:932:7: warning: (this will
>> be reported only once per input file) [enabled by default]
>>
>> (and similar things in trans-stmt.c). You should definitely fix those.
>> Although a non-buildstrap build still works with those warnings, a
>> full bootstrap will fail.


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