diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2017-02-09 15:49:57 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2017-02-09 15:49:57 -0500 |
commit | fc96a5fbc69918ad23f5c5afbe8134aa53d397ef (patch) | |
tree | 79db57cbd046b1810dc39d1a203647938b108423 /src/backend/parser/parse_node.c | |
parent | 404756fe89f62735f6075abb594b54be9c262b27 (diff) | |
download | postgresql-fc96a5fbc69918ad23f5c5afbe8134aa53d397ef.tar.gz postgresql-fc96a5fbc69918ad23f5c5afbe8134aa53d397ef.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/parser/parse_node.c')
0 files changed, 0 insertions, 0 deletions