This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Fix atomic_full_barrier on x86 and x86_64.
- From: Torvald Riegel <triegel at redhat dot com>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: Rich Felker <dalias at libc dot org>, GLIBC Devel <libc-alpha at sourceware dot org>, Richard Henderson <rth at twiddle dot net>, "Carlos O'Donell" <carlos at redhat dot com>
- Date: Mon, 08 Dec 2014 17:38:06 +0100
- Subject: Re: [PATCH] Fix atomic_full_barrier on x86 and x86_64.
- Authentication-results: sourceware.org; auth=none
- References: <1414606736 dot 10085 dot 1 dot camel at triegel dot csb> <20141029203158 dot GU22465 at brightrain dot aerifal dot cx> <1414616100 dot 10085 dot 11 dot camel at triegel dot csb> <Pine dot LNX dot 4 dot 64 dot 1410292151470 dot 15119 at digraph dot polyomino dot org dot uk> <1414621937 dot 10085 dot 67 dot camel at triegel dot csb> <Pine dot LNX dot 4 dot 64 dot 1410292236350 dot 15119 at digraph dot polyomino dot org dot uk> <1416912710 dot 1771 dot 176 dot camel at triegel dot csb>
Ping.
On Tue, 2014-11-25 at 11:51 +0100, Torvald Riegel wrote:
> On Wed, 2014-10-29 at 22:54 +0000, Joseph S. Myers wrote:
> > On Wed, 29 Oct 2014, Torvald Riegel wrote:
> >
> > > So, mfence seems to have been introduced with SSE2. Should I try to
> > > test for SSE2 specifically, or rather assume SSE2 support for i786?
> >
> > I think the i786 directories should be removed; config.guess will never
> > return such a processor name for GNU/Linux at least (I don't know what it
> > returns on Hurd). The comment in sysdeps/i386/i786/Implies suggests it
> > was for PII, but PII was still family 6 (and family 15 came after family
> > 6, I don't think there were any x86 processors with family numbers 7 to
> > 14).
> >
> > So, anything conditional on SSE2 should test for __SSE2__.
>
> How does this updated patch look? The non-SSE full barrier is what,
> AFAIU, GCC emits.
>