This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
RE: malloc and threads
- From: "Mathew, Tisson K" <tisson dot k dot mathew at intel dot com>
- To: libc-alpha at sources dot redhat dot com
- Cc: "Mathew, Tisson K" <tisson dot k dot mathew at intel dot com>
- Date: Wed, 27 Nov 2002 12:10:31 -0800
- Subject: RE: malloc and threads
How can I compile glibc to enable thread-safety? I'm using glibc 2.2.2
Is NO_THREADS define related to thread-safety? Is there a way to turn ON or
turn OFF thread-safety when compiling glibc?
Thanks
-tisson
-----Original Message-----
From: Mathew, Tisson K [mailto:tisson.k.mathew@intel.com]
Sent: Wednesday, November 27, 2002 10:45 AM
To: 'David Boreham'
Cc: libc-alpha@sources.redhat.com
Subject: RE: malloc and threads
I that case malloc protected with mutex should also fail, im not seeing that
Thanks
-tisson
-----Original Message-----
From: David Boreham [mailto:david_list@boreham.org]
Sent: Wednesday, November 27, 2002 9:08 AM
To: libc-alpha@sources.redhat.com
Subject: Re: malloc and threads
> XScale is an ARM based processor
Perhaps there is a bug in the XScale locking code
or in the CPU hardware ?
(The XScale processors have a reputation for
having many hardware bugs which need software
workarounds [compared to the StrongARM] ).