Re: horo(r)logy test fail on solaris (again and solved) - Mailing list pgsql-hackers

From Zdenek Kotala
Subject Re: horo(r)logy test fail on solaris (again and solved)
Date
Msg-id 451A7F39.1000101@sun.com
Whole thread Raw
In response to Re: horo(r)logy test fail on solaris (again and solved)  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: horo(r)logy test fail on solaris (again and solved)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Andrew Dunstan napsal(a):
> 
> 
> Tom Lane wrote:
>> Zdenek Kotala <Zdenek.Kotala@Sun.COM> writes:
>>  
>>> But the question is if the "-fast" flag is good for postgres. The 
>>> -fast flag sets "brutal" floating point optimization and some 
>>> operation should have less precision. Is possible verify that 
>>> floating point operation works well?
>>>     
>>
>> That's a pretty good way to guarantee that you'll break the datetime
>> code.
>>
>>   
> 
> !      | @ 6 years                     | @ 5 years 12 mons 5 days 6 hours
> 
> 
> 
> Doesn't this look odd regardless of what bad results come back from the 
> FP library?

The problem was generated, because -fast option was set only for the 
compiler and not for the linker. Linker takes wrong version of 
libraries. If   -fast is set for both then horology test is OK, but 
question was if float optimalization should generate some problems.
regards, Zdenek


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Faster StrNCpy
Next
From: Tom Lane
Date:
Subject: Re: Faster StrNCpy