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

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

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

Re: glibc 2.2.2 test-double failure

To: Ulrich Drepper <drepper at cygnus dot com>
Subject: Re: glibc 2.2.2 test-double failure
From: Jakub Jelinek <jakub at redhat dot com>
Date: Sat, 17 Feb 2001 01:19:08 +0100
Cc: Glibc hackers <libc-hacker at sources dot redhat dot com>
References: <20010216202728.P768@sunsite.ms.mff.cuni.cz> <m34rxu4e5n.fsf@otr.mynet.cygnus.com>
Reply-To: Jakub Jelinek <jakub at redhat dot com>

On Fri, Feb 16, 2001 at 11:32:36AM -0800, Ulrich Drepper wrote:
> Jakub Jelinek <jakub@redhat.com> writes:
> 
> > I've done make check of 2.2.2 on various platforms, alpha & alphaev6
> > succeeded, ia64 failed with the usual ex5, ex9, ex10 thread tests needing to
> > be killed (it is 4way ia64 FYI),
> 
> I don't see this on a UP.

It looks like both gnupro-1117 and gcc-2.96-75 miscompile spinlock.c at -O2
or -O3 and when things and the first time threads contend on a spinlock they
can go into endless loop.
Don't know more details yet.

	Jakub

Follow-Ups:
- Re: glibc 2.2.2 test-double failure
  - From: H . J . Lu

References:
- glibc 2.2.2 test-double failure
  - From: Jakub Jelinek
- Re: glibc 2.2.2 test-double failure
  - From: Ulrich Drepper

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