This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.

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

Re: gcc bug impacts glibc cvs

To: Franz Sirl <Franz dot Sirl-kernel at lauterbach dot com>
Subject: Re: gcc bug impacts glibc cvs
From: Ulrich Drepper <drepper at redhat dot com>
Date: 12 Mar 2001 12:13:30 -0800
Cc: Jack Howarth <howarth at bromo dot med dot uc dot edu>, libc-alpha at sources dot redhat dot com
References: <Franz Sirl's message of "Mon, 12 Mar 2001 19:52:25 +0100"> <JackHowarth's message of "Mon, 12 Mar 2001 04:02:55 -0800 (PST)"><200103121202.EAA31792@bromo.med.uc.edu><5.0.2.1.2.20010312195016.02eb4738@mail.lauterbach.com><5.0.2.1.2.20010312204650.019b88f8@mail.lauterbach.com>
Reply-To: drepper at cygnus dot com (Ulrich Drepper)

Franz Sirl <Franz.Sirl-kernel@lauterbach.com> writes:

> How will you handle that case then?

As I said before: with a test.  If the one I sent is not sufficient
fix it.

> IMHO the only safe thing to do is to incorporate some kind of
> workaround and unconditionally enable it until GCC is fixed,
> everthing else is just depending on pure luck.

No.  The sources live far too long.  People will use it even when the
problem is fixed.  The policy always has been to have test to check
for the problems.

-- 
---------------.                          ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Red Hat          `--' drepper at redhat.com   `------------------------

References:
- gcc bug impacts glibc cvs
  - From: Jack Howarth
- Re: gcc bug impacts glibc cvs
  - From: Franz Sirl
- Re: gcc bug impacts glibc cvs
  - From: Franz Sirl

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