aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistutil.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2017-02-09 15:49:57 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2017-02-09 15:49:57 -0500
commitcf73c6bfc7148077cda6ff68dae551c0a2674182 (patch)
tree629aac86db36d0cf29cbd38dfc5dba40bb5fd568 /src/backend/access/gist/gistutil.c
parent7786b984825ea720aed3a11ee465dc3d6cfc8d96 (diff)
downloadpostgresql-cf73c6bfc7148077cda6ff68dae551c0a2674182.tar.gz
postgresql-cf73c6bfc7148077cda6ff68dae551c0a2674182.zip
Blind try to fix portability issue in commit 8f93bd851 et al.
The S/390 members of the buildfarm are showing failures indicating that they're having trouble with the rint() calls I added yesterday. There's no good reason for that, and I wonder if it is a compiler bug similar to the one we worked around in d9476b838. Try to fix it using the same method as before, namely to store the result of rint() back into a "double" variable rather than immediately converting to int64. (This isn't entirely waving a dead chicken, since on machines with wider-than-double float registers, the extra store forces a width conversion. I don't know if S/390 is like that, but it seems worth trying.) In passing, merge duplicate ereport() calls in float8_timestamptz(). Per buildfarm.
Diffstat (limited to 'src/backend/access/gist/gistutil.c')
0 files changed, 0 insertions, 0 deletions