C vs. C++ breakage on 4.7 (was Re: [Patch, fortran] PR58007: unresolved fixup hell)

Hans-Peter Nilsson hp@bitrange.com
Tue Jan 28 02:25:00 GMT 2014

On Mon, 27 Jan 2014, Richard Biener wrote:
> >Huh, so we have C for cross-builds and C++ for bootstraps.
> No, we use a C host compiler in both cases. Only stages 2 and 3 build with a C++ compiler.

Tomatos potatoes!  As fortran isn't built until then, it'll be
built as C for cross-builds and C++ for native bootstraps.  Can
we make stage 2 and 3 built with C on the 4.7 branch?

> Richard.
>  I
> >wish we could retire that difference *also* on the 4.7 branch
> >(using either C *or* C++ for *both* would be fine with me FWIW).
> >I believe we're now eperiencing more problems than benefits with
> >that difference, now that the migration is over.
> >
> >> > Looks like you committed C++ code there, in module.c:
> >> Alright; can you try the attached patch?
> >
> >Sorry, not at the moment, but I see Janus took care of that
> >(thanks) and it looks pretty obvious to me.  It'll be noticed
> >when it's committed...
> >
> >brgds, H-P

More information about the Gcc-patches mailing list