This is the mail archive of the gcc@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: Guidelines for building fixincludes for targets?

From: Andrew Pinski <pinskia at physics dot uc dot edu>
To: Joe Buck <Joe dot Buck at synopsys dot com>
Cc: "Aaron W. LaFramboise" <aaronavay62 at aaronwl dot com>, "E. Weddington" <ericw at evcohs dot com>, gcc <gcc at gcc dot gnu dot org>
Date: Fri, 22 Oct 2004 18:05:01 -0400
Subject: Re: Guidelines for building fixincludes for targets?
References: <417934E5.7050603@evcohs.com> <4179772E.1040904@aaronwl.com> <417979DF.9040306@evcohs.com> <8B8AC0C0-2471-11D9-8879-000A95D692F4@physics.uc.edu> <20041022145518.A27645@synopsys.com>

On Oct 22, 2004, at 5:55 PM, Joe Buck wrote:

On Fri, Oct 22, 2004 at 05:30:07PM -0400, Andrew Pinski wrote:
Almost all targets today need fixincludes, including linux.
It would seem that any fixincludes support needed on a glibc-based
platform is a bug in glibc, right?


Yes and already fixed in newer versions of glibc but people
still run older versions of glibc.  I am talking about fixing
up pthreads.h here were they used __thread which was nothing
until TLS support was added to GCC.

-- Pinski

References:
- Guidelines for building fixincludes for targets?
  - From: E. Weddington
- Re: Guidelines for building fixincludes for targets?
  - From: Aaron W. LaFramboise
- Re: Guidelines for building fixincludes for targets?
  - From: E. Weddington
- Re: Guidelines for building fixincludes for targets?
  - From: Andrew Pinski
- Re: Guidelines for building fixincludes for targets?
  - From: Joe Buck

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