This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/12403] futex issues with --enable-kernel=2.6.22 to 2.6.28
- From: "allan at archlinux dot org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Sun, 16 Jan 2011 09:53:24 +0000
- Subject: [Bug nptl/12403] futex issues with --enable-kernel=2.6.22 to 2.6.28
- Auto-submitted: auto-generated
- References: <bug-12403-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12403
--- Comment #1 from Allan McRae <allan at archlinux dot org> 2011-01-16 09:53:22 UTC ---
Naively trying to locate the source of this bug... Generating a list of files
that have #ifdef/#ifndef on the __ASSUME_PRIVATE_FUTEX and
__ASSUME_FUTEX_CLOCK_REALTIME defines (assuming this is not some more complex
interaction) and are x86_64 specific (as this does not occur on i686 builds)
gives:
nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S
nptl/sysdeps/unix/sysv/linux/x86_64/lowlevelrobustlock.S
nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S
nptl/sysdeps/unix/sysv/linux/x86_64/pthread_rwlock_timedrdlock.S
nptl/sysdeps/unix/sysv/linux/x86_64/pthread_rwlock_timedwrlock.S
If we further assume that the bug requires a nested #ifdef for these two
values, that restricts the issue to small parts of the last three files and
given the test suite failures we can exclude the first of those.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.