This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Add a barrier in the double fma implementation
- From: Roland McGrath <roland at hack dot frob dot com>
- To: Aurelien Jarno <aurelien at aurel32 dot net>
- Cc: libc-alpha at sources dot redhat dot com, Joseph Myers <joseph at codesourcery dot com>
- Date: Wed, 15 Feb 2012 12:17:49 -0800 (PST)
- Subject: Re: [PATCH] Add a barrier in the double fma implementation
- References: <20120215192056.GD17446@hall.aurel32.net>
I try to avoid knowing anything about floating-point. But it seems like
this would be an issue for applications too. I wonder if fetestexcept et
al shouldn't have barriers themselves? I guess the public calls are actual
functions, so they are all implicit barriers--but does that hold under
static linking plus massive link-time interprocedural optimization (which
could come along some day even if it's not all here yet).
Is there any use of the libc_fe* calls in which a barrier is *not*
appropriate?
Thanks,
Roland