Skip site navigation (1) Skip section navigation (2)

Re: spinlocks on HP-UX

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: Kevin(dot)Grittner(at)wicourts(dot)gov
Cc: heikki(dot)linnakangas(at)enterprisedb(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us, robertmhaas(at)gmail(dot)com, manabu(dot)ori(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: spinlocks on HP-UX
Date: 2011-12-29 00:49:42
Message-ID: 20111229.094942.1687009016210410891.t-ishii@sraoss.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackers
OT:

Please use mail address "manabu(dot)ori(at)gmail(dot)com", not
"manabu(dot)ori(at)gmailc(dot)com" when following this thread.  I accidently made
a mistake when I posted the first mail in this thread.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

> Tom Lane  wrote:
>  
>> a configure test only proves whether the build machine can deal
>> with the flag, not whether the machine the executables will
>> ultimately run on knows what the flag means.  We cannot assume that
>> the build and execution boxes are the same.  (In general,
>> AC_TRY_RUN tests are best avoided because of this.)
>  
> I understand why that is important in general, but as a shop which
> builds from source, and is fine with a separate build for each
> hardware model / OS version combination, it would be great if any
> optimizations which are only available if you *do* assume that the
> build machine and the run machine are the same (or at lease
> identical) could be enabled with some configure switch.  Maybe
> something like --enable-platform-specific-optimizations.
>  
> I don't know if any such possible optimizations currently exist, I'm
> just saying that if any are identified, it would be nice to have the
> option of using them.
>  
> -Kevin

In response to

pgsql-hackers by date

Next:From: Manabu OriDate: 2011-12-29 02:36:20
Subject: Re: spinlocks on HP-UX
Previous:From: Kevin GrittnerDate: 2011-12-29 00:35:01
Subject: Re: spinlocks on HP-UX

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group