Re: [HACKERS] pgtypeslib/timestamp problem

2003-03-27 Thread Tom Lane
Michael Meskes <[EMAIL PROTECTED]> writes: > Tom, I take it you have released gcc 3.2 right? It seems my ione is > based on a CVS prerelease: It's whatever came with RH 8.0 ... $ gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2/specs Configured with: ../configure --prefix=/usr --m

Re: [HACKERS] pgtypeslib/timestamp problem

2003-03-27 Thread Michael Meskes
On Thu, Mar 27, 2003 at 09:07:48AM -0500, Tom Lane wrote: > FWIW, I get the correct answer in CVS tip on Red Hat Linux 8.0, which > is using gcc 3.2 (and -O2, per defaults in our makefiles): Thanks Tom. I just wonder what's different in my makefile. It just does: include $(top_builddir)/src/Makef

Re: [HACKERS] pgtypeslib/timestamp problem

2003-03-27 Thread Tom Lane
Michael Meskes <[EMAIL PROTECTED]> writes: > So here's the question comojng out of this all, anyone out here with an > idea why the timestamp "Wed Jul 12 17:34:29 2000" becomes "Wed Jul 12 > 4649:34:26.02 2000" when putting it into timestamp format and back > out. The function is almost identic

[HACKERS] pgtypeslib/timestamp problem

2003-03-27 Thread Michael Meskes
I found it, well not really that is. It seems the problem is triggered by some gcc optimization. I'm using gcc 3.2.3. If I specify -O2 it does not work correctly, without optimization it does. Now the big question is which optimization is causing trouble. It certainly is not -ffast-math as I do i