This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
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: Mikael Morin <mikael dot morin at sfr dot fr>
- Cc: gcc-patches <gcc-patches at gcc dot gnu dot org>, gfortran <fortran at gcc dot gnu dot org>
- Date: Mon, 27 Jan 2014 09:03:28 -0500 (EST)
- Subject: 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>
On Mon, 27 Jan 2014, Mikael Morin wrote:
> Le 27/01/2014 02:56, Hans-Peter Nilsson a écrit :
> > On Sun, 26 Jan 2014, Mikael Morin wrote:
> >> Le 18/01/2014 21:17, Mikael Morin a écrit :
> >>> Well, I guess that due to the touchy nature of the bug, there are cases
> >>> that work by luck on old versions and fail (by unluck) on newer ones.
> >>> Thus, I will backport in a few days to 4.8 and 4.7.
> >>>
> >> I added the following hardening to the patch on the 4.8 backport
> >> (http://gcc.gnu.org/r207117 and attached) and forward-ported it to trunk
> >> (http://gcc.gnu.org/r207118) as well.
> >> 4.7 will come in an hour or so.
> >
> > Did you bootstrap & test the 4.7 backport?
> >
> Yes, works like a charm here.
Huh, so we have C for cross-builds and C++ for bootstraps. 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