Re: Optimization levels when compiling PostgreSQL...

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: Sean Chittenden <sean(at)chittenden(dot)org>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Curt Sampson <cjs(at)cynic(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Optimization levels when compiling PostgreSQL...
Date: 2002-09-10 23:05:20
Message-ID: Pine.LNX.4.44.0209101843350.1307-100000@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Neil Conway writes:

> Also, if -O3 *is* a good compiler option, I dislike the idea of
> enabling it for your own packages but no one else's. IMHO distributors
> should not futz with packages more than is strictely necessary, and a
> change like this seems both unwarranted, and potentially dangerous. If
> -O3 is a good idea, we should make the change for the appropriate
> platforms in the official source, and let it get the widespread
> testing it requires.

I disagree. Choosing the compiler options is exactly the job of the
installer, packager, or distributor. That's why you can specify CFLAGS on
the command line after all, and most distributors' build environments make
use of that.

I don't think we're doing anyone a service if we spread wild speculations
about how risky certain compiler options are. If your compiler creates
broken code, don't use it. Packagers are expected to know about their
compiler. If they create broken packages and behave irresponsibly about
it they won't be making packages much longer.

--
Peter Eisentraut peter_e(at)gmx(dot)net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephan Szabo 2002-09-10 23:25:10 Re: problem with new autocommit config parameter and jdbc
Previous Message Peter Eisentraut 2002-09-10 23:05:03 Re: Optimization levels when compiling PostgreSQL...