Re: Bug fix for glibc broke freebsd build in REL_11_STABLE
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Andrew Gierth <andrew@tao11.riddles.org.uk>,
Victor Wagner <vitus@wagner.pp.ru>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2018-09-04T23:02:02Z
Lists: pgsql-hackers
Andres Freund <andres@anarazel.de> writes: > ... Note that we've previously encountered similar issues > on gcc, which is why we've tried to force gcc's hand with > -fexcess-precision=standard. Right. Annoying that clang doesn't have that. We can't realistically program around an issue that might or might not show up depending on the whims of the compiler's register allocation. > I kinda wonder if we should add -mno-x87 or such in configure when we > detect clang, obviously it doesn't deal correctly with this. Seems worth looking into, but what happens if someone tries to compile for x87 hardware? Or do we care anymore? regards, tom lane
Commits
-
Error out for clang on x86-32 without SSE2 support, no -fexcess-precision.
- 978515df2278 9.3.25 landed
- 29196e13cd70 9.4.20 landed
- dbbc98a9ef67 9.5.15 landed
- e553997e3f59 9.6.11 landed
- 1b8f09dbd352 10.6 landed
- 84f14fb78852 11.0 landed
- bd1463e348fc 12.0 landed
-
Fix 8a934d677 for libc++ and make more include order resistant.
- 1f349aa7d9a6 11.0 cited