From 6d3f1a39c14b12026df84f386875b094e3652990 Mon Sep 17 00:00:00 2001 From: Szabolcs Nagy Date: Tue, 13 Nov 2012 19:59:02 +0100 Subject: [PATCH] math: turn off the STRICT_ASSIGN workaround by default the volatile hack in STRICT_ASSIGN is only needed if assignment is not respected and excess precision is kept. gcc -fexcess-precision=standard and -ffloat-store both respect assignment and musl use these flags by default. i kept the macro for now so the workaround may be used for bad compilers in the future. --- src/internal/libm.h | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/src/internal/libm.h b/src/internal/libm.h index dfecd836..46c4b564 100644 --- a/src/internal/libm.h +++ b/src/internal/libm.h @@ -157,16 +157,14 @@ long double __tanl(long double, long double, int); long double __polevll(long double, const long double *, int); long double __p1evll(long double, const long double *, int); -// FIXME: not needed when -fexcess-precision=standard is supported (>=gcc4.5) -/* - * Attempt to get strict C99 semantics for assignment with non-C99 compilers. - */ -#if 1 +#if 0 +/* Attempt to get strict C99 semantics for assignment with non-C99 compilers. */ #define STRICT_ASSIGN(type, lval, rval) do { \ volatile type __v = (rval); \ (lval) = __v; \ } while (0) #else +/* Should work with -fexcess-precision=standard (>=gcc-4.5) or -ffloat-store */ #define STRICT_ASSIGN(type, lval, rval) ((lval) = (type)(rval)) #endif -- 2.25.1