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: [fixincludes, patch] PR30272 Build failure under SGI Irix (GFortran)

From: "Bruce Korb" <bkorb at gnu dot org>
To: "Daniel Franke" <franke dot daniel at gmail dot com>
Cc: gcc-patches at gcc dot gnu dot org, "Philippe Schaffnit" <philippe at access dot rwth-aachen dot de>
Date: Wed, 24 Jan 2007 15:26:29 -0800
Subject: Re: [fixincludes, patch] PR30272 Build failure under SGI Irix (GFortran)
References: <200701242348.51073.franke.daniel@gmail.com> <668c430c0701241501r36ac6bf8taa48d97f0c632f79@mail.gmail.com> <200701250018.29552.franke.daniel@gmail.com>

On 1/24/07, Daniel Franke <franke.daniel@gmail.com> wrote:

> Looks reasonable to me.  How about the maintenance branches?
>  - Bruce

I do not know whether Philippe already gave them a try.
If the same error occurs, it should be safe to port the patch to 4.1/4.2?!


Yes, it should be safe.  After all, you are removing bogus code with
this change.  If it is bogus for mainline, it would surely be bogus for
the stable ports, too, yes?  I went to a lot of trouble to ensure that
this fixincludes stuff does things in a highly reproducible, stable and
safe fashion.  So, yes, it should be safe.

Cheers - Bruce

Follow-Ups:
- Re: [fixincludes, patch] PR30272 Build failure under SGI Irix (GFortran)
  - From: Daniel Franke

References:
- [fixincludes, patch] PR30272 Build failure under SGI Irix (GFortran)
  - From: Daniel Franke
- Re: [fixincludes, patch] PR30272 Build failure under SGI Irix (GFortran)
  - From: Bruce Korb
- Re: [fixincludes, patch] PR30272 Build failure under SGI Irix (GFortran)
  - From: Daniel Franke

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