Re: Call for port reports - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Call for port reports
Date
Msg-id 200310260038.h9Q0cuH00120@candle.pha.pa.us
Whole thread Raw
In response to Re: Call for port reports  (Noèl Köthe <noel@debian.org>)
Responses opteron port [was: Re: Call for port reports]
List pgsql-hackers
No�l K�the wrote:
-- Start of PGP signed section.
> Am Sa, den 25.10.2003 schrieb No?l K?the um 01:17:
> > > It is time for people to report their port testing.  Please test against
> > > current CVS or beta5 and report your 'uname -a'.
> > > 
> > > The current list is at:
> > > 
> > >     http://candle.pha.pa.us/main/writings/pgsql/sgml/supported-platforms.html
> > 
> > here are some build reports. Its all on Debian GNU/Linux with different
> > architectures:
> 
> ======================
>  All 93 tests passed.
> ======================
>  
> rm regress.o
> make[2]: Leaving directory `/home/noel/pgsql/src/test/regress'
> make[1]: Leaving directory `/home/noel/pgsql/src/test'
> noel@pergolesi:~/pgsql$ uname -a
> Linux pergolesi 2.4.22 #1 SMP Mon Aug 25 20:56:25 CEST 2003 i686 GNU/Linux
> 
> It says i686 but its AMD Opteron:
> 
> noel@pergolesi:~/pgsql$ cat /proc/cpuinfo |more
> processor       : 0
> vendor_id       : AuthenticAMD
> cpu family      : 15
> model           : 5
> model name      : AMD Opteron(tm) Processor 240
> stepping        : 1
> cpu MHz         : 1394.299
> cache size      : 1024 KB
> ...

I am confused how to handle this.  Is this running in 32-bit mode?  I am
inclined to mention Opteron only when tested in 64-bit mode, because I
think we all assume a 32-bit Opteron is the same as a standard
AMD/Intel.  Does uname report differently in 64-bit mode.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Call for port reports
Next
From: Bruce Momjian
Date:
Subject: Re: Call for port reports