Re: GiST penalty functions [PoC] - Mailing list pgsql-hackers

From Greg Stark
Subject Re: GiST penalty functions [PoC]
Date
Msg-id CAM-w4HNf34gYFKug2Q2gnbpA8hDvtTbhrNoqMHgYD0za=M0yPg@mail.gmail.com
Whole thread Raw
In response to Re: GiST penalty functions [PoC]  (Andrew Borodin <borodin@octonica.com>)
Responses Re: GiST penalty functions [PoC]
Re: GiST penalty functions [PoC]
List pgsql-hackers
On Thu, Sep 8, 2016 at 9:29 AM, Andrew Borodin <borodin@octonica.com> wrote:
>>autoconf check for IEEE 754 floats
> Autoconf man says folowing:
>>it is safe to assume IEEE-754 in most portable code these days
> https://www.gnu.org/software/autoconf/manual/autoconf.html#Floating-Point-Portability


Personally I wouldn't be very happy about an IEEE754 assumption. I did
go to the trouble of testing Postgres on a VAX and we fixed the few
instances where it had such dependencies for a net gain. If we
intentionally put a dependency in in one place then we'll never be
able to determine anywhere else where there are unintentional
dependencies.

I haven't followed the thread closely but I'm puzzled why you would
need to use bit twiddling to set a floating point number. Isn't there
a perfectly good way to calculate the value you want using ldexp() and
other standard C library functions?

-- 
greg



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: GiST optimizing memmoves in gistplacetopage for fixed-size updates [PoC]
Next
From: Adam Brightwell
Date:
Subject: Re: COPY command with RLS bug