Re: gcc: why optimize for size flag is not the default - Mailing list pgsql-hackers

From Tom Lane
Subject Re: gcc: why optimize for size flag is not the default
Date
Msg-id 26016.1236775361@sss.pgh.pa.us
Whole thread Raw
In response to Re: gcc: why optimize for size flag is not the default  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: gcc: why optimize for size flag is not the default  (Greg Stark <stark@enterprisedb.com>)
Re: gcc: why optimize for size flag is not the default  (Marko Kreen <markokr@gmail.com>)
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> Nikhil Sontakke wrote:
>> I was wondering why -Os is not used in place of -O2 while compiling the
>> Postgres sources with gcc.

> There's no free lunch.

In any case, this sort of choice is generally something that ought to be
applied at a distro level.  If, say, Fedora or Debian chose to use -Os
uniformly across all their packages, then there might be a meaningful
amount of space saved in the aggregate.  As far as I know, though, -Os
is not the preferred choice in any distro, which ought to tell you
something ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Has anybody think about changing BLCKSZ to an option of initdb?
Next
From: Simon Riggs
Date:
Subject: Re: idea, proposal: only preloadable libraries (conditional load)