Re: spinlocks on HP-UX

From: Manabu Ori <manabu(dot)ori(at)gmail(dot)com>
To: Kevin Grittner <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, ishii(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: spinlocks on HP-UX
Date: 2011-12-29 02:37:22
Message-ID: CADWW1HH36neiCHvfWNut7Gfxhd8Pt55_tWRdqewqy5UZOCAipw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > 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.

I can't say the right way to go for now, but I'd like binary
packages could enjoy the effect of my patch as far as possible so
that I made lwarx hint test run in configure runtime.

Regards,
Manabu Ori

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Boszormenyi Zoltan 2011-12-29 09:46:23 Re: ECPG FETCH readahead
Previous Message Manabu Ori 2011-12-29 02:36:20 Re: spinlocks on HP-UX