From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Uncle George <gatgul(at)voicenet(dot)com> |
Cc: | pgsql-ports(at)postgreSQL(dot)org |
Subject: | Re: [PORTS] RedHat6.0 & Alpha |
Date: | 1999-07-15 03:13:44 |
Message-ID: | 199907150313.XAA27280@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-ports |
> Well, a reply, anyway
>
> 1) reltime & abstime values are stored in the DB as 4 byte values. The
> definitions for abstime&reltime are also stored in the DB ( this from empiracle
> debugging ) . If you do not plan to embrace the notion of #of seconds >
> 2^(32-1), and you dont want to alter the DB notion that storage is 4 bytes then
>
> typedef int32 Absolutetime;
> typedef int32 Relativetime;
>
> would appear to be most preferable & more stable (majic #'s work ) than
>
> typedef time_t Absolutetime;
> typedef time_t Relativetime;
>
> This is not a complete solution , as there are still some sign extension
> problems as demonstratable by the regression tests.
> If you want to use 64bit Absolutetime & reltimes, then you should adjust (
> or make more abstract ) the concept of abstime&reltime. BUT
> THIS IS NOT A PORTING ISSUE! I would just like to get the abstime*reltime to
> behave much like the 32bit folks.
Makes sense. Using time_t does not make sense if we are forcing
everything to 4 bytes.
>
> 2) Can u add HAS_LONG_LONG to $(CFLAGS)
> I dont have long long, but it turns on some code ( somewhere ) that fixes
> another problem.
Check configure. It runs a test to see if long long works, and sets that
in include/config.h.
>
> 3) -mieee informs the egcs compiler fot the alpha to inject 'trapb'
> instructions at various places in a floating point computation. The trapb is a
> pipeline stall forcing the processor to stop issueing instructions until all
> current instructions in the pipeline have executed. This is done to capture a
> possible 'fault' at a resomable time so you can backtrack to the instruction
> that faulted and take some corrective measure. There are also rules for
> backtracing, and repairing. The usage of -mieee inserted these trapb's all over
> the place. The current egcs compiler appears to do a better job at it For
> purely int operations, then a module need not be enhanced by the -mieee switch.
I am stumped on why we even need -mieee, but someone supplied a patch to
add it.
>
> 4) I'd give u some patches, but still getting the regression tests to work.
> Where do I get 6.5.1, so I can work with that as a base
Go to ftp.postgresql.org, and get the "snapshot". That will be 6.5.1 on
July 19th.
> 5) What is the floating point rounding set to ( up/down ). There seems to be an
> extra digit of precision in ur i386, where the alpha port appears to round up (
> and have 1 digit less :( )
Not sure where that is set. Would be fpsetround() on BSD/OS, however, I
don't see us setting it anywhere, so my guess is that we are using the
OS default for this.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Adriaan Joubert | 1999-07-15 05:53:45 | Re: [HACKERS] header files for spi.h/trigger.h] |
Previous Message | Bruce Momjian | 1999-07-15 03:08:23 | Re: [HACKERS] header files for spi.h/trigger.h] |
From | Date | Subject | |
---|---|---|---|
Next Message | Uncle George | 1999-07-15 10:44:12 | Re: [PORTS] RedHat6.0 & Alpha |
Previous Message | Uncle George | 1999-07-15 00:39:24 | Re: [PORTS] RedHat6.0 & Alpha |