This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: C vs. C++ breakage on 4.7 (was Re: [Patch, fortran] PR58007: unresolved fixup hell)
- From: Hans-Peter Nilsson <hp at bitrange dot com>
- To: Richard Biener <richard dot guenther at gmail dot com>
- Cc: Mikael Morin <mikael dot morin at sfr dot fr>, gcc-patches <gcc-patches at gcc dot gnu dot org>, gfortran <fortran at gcc dot gnu dot org>
- Date: Mon, 27 Jan 2014 21:25:32 -0500 (EST)
- Subject: Re: C vs. C++ breakage on 4.7 (was Re: [Patch, fortran] PR58007: unresolved fixup hell)
- Authentication-results: sourceware.org; auth=none
- References: <52C55062 dot 3000809 at sfr dot fr> <CAKwh3qhso_rYFdibfTP=QP2rUXpbFXjnV3MJJLVOAkyz8N4whA at mail dot gmail dot com> <52D13696 dot 8000909 at sfr dot fr> <CAKwh3qhWcfiSAjS5x06w-brOkStjfk+qJejBT+utCCoSTpzViw at mail dot gmail dot com> <52DAE144 dot 8010400 at sfr dot fr> <52E519CE dot 4030106 at sfr dot fr> <alpine dot BSF dot 2 dot 02 dot 1401262047450 dot 70119 at arjuna dot pair dot com> <52E61B35 dot 5040605 at sfr dot fr> <alpine dot BSF dot 2 dot 02 dot 1401270854430 dot 37506 at arjuna dot pair dot com> <5e723074-189c-40d2-94bc-111d90a88566 at email dot android dot com>
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
>
>
- References:
- [Patch, fortran] PR58007: unresolved fixup hell
- Re: [Patch, fortran] PR58007: unresolved fixup hell
- Re: [Patch, fortran] PR58007: unresolved fixup hell
- Re: [Patch, fortran] PR58007: unresolved fixup hell
- Re: [Patch, fortran] PR58007: unresolved fixup hell
- Re: [Patch, fortran] PR58007: unresolved fixup hell
- Re: [Patch, fortran] PR58007: unresolved fixup hell
- Re: [Patch, fortran] PR58007: unresolved fixup hell
- C vs. C++ breakage on 4.7 (was Re: [Patch, fortran] PR58007: unresolved fixup hell)
- Re: C vs. C++ breakage on 4.7 (was Re: [Patch, fortran] PR58007: unresolved fixup hell)