Re: gcc: why optimize for size flag is not the default
От | Marko Kreen |
---|---|
Тема | Re: gcc: why optimize for size flag is not the default |
Дата | |
Msg-id | e51f66da0903110651o5502ee38p910be2a5e8fe8388@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: gcc: why optimize for size flag is not the default (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: gcc: why optimize for size flag is not the default
|
Список | pgsql-hackers |
On 3/11/09, Tom Lane <tgl@sss.pgh.pa.us> wrote: > 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 ... Linux kernel is moving to use -Os everywhere. AFAIK their argument is that kernel code should not be doing anything CPU-intensive, thus minimal cache usage is more important than unrolled loops. This also seems to hint that -Os is not really appropriate to Postgres. Although it would be good fit for eg. PgBouncer. -- marko
В списке pgsql-hackers по дате отправления: