On Thu, 2020-04-30 at 23:38 +0200, Jakub Jelinek wrote:
> On Thu, Apr 30, 2020 at 05:31:22PM -0400, David Malcolm wrote:
> > On Thu, 2020-04-30 at 23:26 +0200, Jakub Jelinek wrote:
> > > On Thu, Apr 30, 2020 at 05:18:13PM -0400, David Malcolm wrote:
> > > > Thanks for working on this; sorry for getting these wrong.
> > > >
> > > > Is is possible to build gfortran without C and C++? If so,
> > > > then if
> > > > I'm
> > >
> > > It is possible without C++, but not without C.
> > >
> > > E.g. --enable-languages=fortran,go will actually enable
> > > c,fortran,go,lto.
> > > *,c,*)
> > > ;;
> > > *)
> > > enable_languages=c,${enable_languages}
> > > ;;
> > > So, strictly speaking the #ifdef CL_C isn't needed there, so if
> > > you
> > > want,
> > > I can drop that #ifdef and only use CL_CXX ifdef.
> >
> > Thanks.
> >
> > Perhaps a silly question, but does the patch give the right answers
> > if
> > someone does that? (which I think is equivalent to "Are there any
> > options labeled with both Fortran and C++ but not C that are
> > documented
> > in gcc/Warning-Options.html"?)
>
> ATM all the -W* options with CL_Fortran in the mask
> are either CL_C | CL_CXX | CL_Fortran ... | CL_WARNING,
> or CL_Fortran ... | CL_WARNING (not enabled for anything but Fortran)
>
Thanks.
Let's go with your second patch then (CL_C & CL_CXX).
Dave
