Re: Interval aggregate regression failure (expected seems

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paesold <mpaesold(at)gmx(dot)at>, Michael Glaesemann <grzm(at)myrealbox(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Interval aggregate regression failure (expected seems
Date: 2005-11-07 19:25:35
Message-ID: 87acggdzv4.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


c.f.:

`-ffloat-store'
Do not store floating point variables in registers, and inhibit
other options that might change whether a floating point value is
taken from a register or memory.

This option prevents undesirable excess precision on machines such
as the 68000 where the floating registers (of the 68881) keep more
precision than a `double' is supposed to have. Similarly for the
x86 architecture. For most programs, the excess precision does
only good, but a few programs rely on the precise definition of
IEEE floating point. Use `-ffloat-store' for such programs, after
modifying them to store all pertinent intermediate computations
into variables.

--
greg

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Cave-Ayland 2005-11-07 19:44:14 Any advice about function caching?
Previous Message Greg Stark 2005-11-07 19:22:37 Re: Interval aggregate regression failure (expected seems

Browse pgsql-patches by date

  From Date Subject
Next Message Gregory Maxwell 2005-11-07 20:07:15 Re: Interval aggregate regression failure (expected seems
Previous Message Greg Stark 2005-11-07 19:22:37 Re: Interval aggregate regression failure (expected seems