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: GCC Status Report (2005-03-09)

From: Florian Weimer <fw at deneb dot enyo dot de>
To: Joe Buck <Joe dot Buck at synopsys dot COM>
Cc: Andrew Pinski <pinskia at physics dot uc dot edu>, Greg Schafer <gschafer at zip dot com dot au>, gcc at gcc dot gnu dot org, Mark Mitchell <mark at codesourcery dot com>
Date: Fri, 11 Mar 2005 10:38:31 +0100
Subject: Re: GCC Status Report (2005-03-09)
References: <200503092251.j29Mpqmt000736@sethra.codesourcery.com><20050309231540.GA3474@tigers-lfs.nsw.bigpond.net.au><02f5887efbb7507276159a1cdb8c0141@physics.uc.edu><20050310010249.GA32393@synopsys.com>

* Joe Buck:

> If it is only Debian on non-shipped platforms, it would be reasonable to
> ask the Debian x64-64 people to apply the one-line patch to glibc pointed
> to by the PR.  It could be a hassle for them now because of the sarge
> freeze, though, so maybe fixincludes would be the way to go.

AMD64 is not covered by the freeze.  sarge will be released with
GNU libc 2.3.2, I believe, so it's not clear to me if it is affected at all.

References:
- GCC Status Report (2005-03-09)
  - From: Mark Mitchell
- Re: GCC Status Report (2005-03-09)
  - From: Greg Schafer
- Re: GCC Status Report (2005-03-09)
  - From: Andrew Pinski
- Re: GCC Status Report (2005-03-09)
  - From: Joe Buck

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