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

From Grzegorz Jaskiewicz
Subject Re: gcc: why optimize for size flag is not the default
Date
Msg-id 3BBC3658-CCCD-4331-9CA4-06ED9C75A65B@pointblue.com.pl
Whole thread Raw
In response to Re: gcc: why optimize for size flag is not the default  (Marko Kreen <markokr@gmail.com>)
Responses Re: gcc: why optimize for size flag is not the default  ("A.M." <agentm@themactionfaction.com>)
List pgsql-hackers
On 11 Mar 2009, at 13:51, Marko Kreen wrote:

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

while it might be right in case of linux kernel (which I won't agree  
totally with personally), I don't see any reason to compare it with  
postgresql.
Kernel is extensively use by everything in system, hence their  
reasoning. Postgresql is an application.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: idea, proposal: only preloadable libraries (conditional load)
Next
From: "A.M."
Date:
Subject: Re: gcc: why optimize for size flag is not the default