diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2018-04-29 18:15:16 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2018-04-29 18:15:16 -0400 |
| commit | 59c2df3ae8947c4c06217d1b330cfa529f480e17 (patch) | |
| tree | 508641935235fa356a9f6d9bf51291c3a9bc653c /src/timezone/strftime.c | |
| parent | 37c02b2b0a146e623ff6d350f89310a5cfad25e0 (diff) | |
Avoid wrong results for power() with NaN input on more platforms.
Buildfarm results show that the modern POSIX rule that 1 ^ NaN = 1 is not
honored on *BSD until relatively recently, and really old platforms don't
believe that NaN ^ 0 = 1 either. (This is unsurprising, perhaps, since
SUSv2 doesn't require either behavior.) In hopes of getting to platform
independent behavior, let's deal with all the NaN-input cases explicitly
in dpow().
Note that numeric_power() doesn't know either of these special cases.
But since that behavior is platform-independent, I think it should be
addressed separately, and probably not back-patched.
Discussion: https://postgr.es/m/75DB81BEEA95B445AE6D576A0A5C9E936A73E741@BPXM05GP.gisp.nec.co.jp
Diffstat (limited to 'src/timezone/strftime.c')
0 files changed, 0 insertions, 0 deletions