| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Yuya Watari <watari(dot)yuya(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Keep compiler silence (clang 10, implicit conversion from 'long' to 'double' ) |
| Date: | 2019-11-06 02:43:59 |
| Message-ID: | CA+hUKGJrLQs7Q8ff-6DYySX2LSxtDEP-nk7zDfZFFBuyj6Xpww@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 6, 2019 at 3:33 PM Yuya Watari <watari(dot)yuya(at)gmail(dot)com> wrote:
> However, this behavior depends on the platform architecture. As you
> have said, C language does not always follow IEEE-754. I think adding
> explicit checking of NaN is necessary.
I'm curious about this point. C may not require IEEE 754 (for
example, on current IBM mainframe and POWER hardware you can opt for
IBM hex floats, and on some IBM platforms that is the default, and the
C compiler isn't breaking any rules by doing that; the only other
floating point format I've heard of is VAX format, long gone, but
perhaps allowed by C). But PostgreSQL effectively requires IEEE 754
since commit 02ddd499322ab6f2f0d58692955dc9633c2150fc, right?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ideriha.takeshi@fujitsu.com | 2019-11-06 02:55:30 | RE: Global shared meta cache |
| Previous Message | Amit Kapila | 2019-11-06 02:39:54 | Re: cost based vacuum (parallel) |