This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Update to new generic semaphore algorithm v2
- From: Florian Weimer <fweimer at redhat dot com>
- To: Andreas Schwab <schwab at suse dot de>
- Cc: Torvald Riegel <triegel at redhat dot com>, "Carlos O'Donell" <carlos at redhat dot com>, GLIBC Devel <libc-alpha at sourceware dot org>
- Date: Thu, 07 Feb 2019 17:08:31 +0100
- Subject: Re: [PATCH] Update to new generic semaphore algorithm v2
- References: <1421111716.23151.35.camel@triegel.csb> <mvmzhr7yjwh.fsf@suse.de>
* Andreas Schwab:
> This has the effect that a semaphore that is shared between a x86-64 and
> a x86-32 process no longer yields the same value, because the latter
> does not define __HAVE_64B_ATOMICS.
Hasn't this been reported before? I think we decided back then that it
wasn't a bug. Other process-shared synchronization objects (mutexes,
condition variables) had the same problem from the start.
Do you have new information that would call for a re-evaluation of this
decision?
Thanks,
Florian