[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gcc
Subject:    Re: GCC Status Report (2005-03-09)
From:       Joe Buck <Joe.Buck () synopsys ! COM>
Date:       2005-03-10 1:02:49
Message-ID: 20050310010249.GA32393 () synopsys ! com
[Download RAW message or body]

On Wed, Mar 09, 2005 at 06:18:58PM -0500, Andrew Pinski wrote:
> On Mar 9, 2005, at 6:15 PM, Greg Schafer wrote:
> 
> >This is rather critical, yet a bugmaster saw fit to remove the 4.0.0 
> >target
> >milestone on this bug:
> >
> >  http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20166
> >
> >Any chance of making this one a high priority?
> 
> Of course this is a glibc bug and not really a gcc bug.

How many people does this affect?  Does anyone know which distros
have an affected glibc?  (Debian on x86_64, but that's not a supported
platform for sarge, so folks on that platform are probably up to patching
their glibc).

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.



[prev in list] [next in list] [prev in thread] [next in thread]