On Thu, Dec 29, 2011 at 11:37:22AM +0900, Manabu Ori 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. > > 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.
Was there any conclusion to this discussion? -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
