aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistbuildbuffers.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2018-01-18 11:09:44 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2018-01-18 11:09:44 -0500
commit31635bc1d1070fed06740e29c50060b96b60793d (patch)
tree81754d4d0cae9d17d66c89e37b90b640abe14efe /src/backend/access/gist/gistbuildbuffers.c
parent4eae1e6f5da8e7cd011c483d867b5bd8e92c7955 (diff)
downloadpostgresql-31635bc1d1070fed06740e29c50060b96b60793d.tar.gz
postgresql-31635bc1d1070fed06740e29c50060b96b60793d.zip
Extend configure's __int128 test to check for a known gcc bug.
On Sparc64, use of __attribute__(aligned(8)) with __int128 causes faulty code generation in gcc versions at least through 5.5.0. We can work around that by disabling use of __int128, so teach configure to test for the bug. This solution doesn't fix things for the case of cross-compiling with a buggy compiler; to support that nicely, we'd need to add a manual disable switch. Unless more such cases turn up, it doesn't seem worth the work. Affected users could always edit pg_config.h manually. In passing, fix some typos in the existing configure test for __int128. They're harmless because we only compile that code not run it, but they're still confusing for anyone looking at it closely. This is needed in support of commit 751804998, so back-patch to 9.5 as that was. Marina Polyakova, Victor Wagner, Tom Lane Discussion: https://postgr.es/m/0d3a9fa264cebe1cb9966f37b7c06e86@postgrespro.ru
Diffstat (limited to 'src/backend/access/gist/gistbuildbuffers.c')
0 files changed, 0 insertions, 0 deletions