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

From Nikhil Sontakke
Subject gcc: why optimize for size flag is not the default
Date
Msg-id a301bfd90903110114l10cd3e03s3534bf6e998d53d@mail.gmail.com
Whole thread Raw
Responses Re: gcc: why optimize for size flag is not the default
List pgsql-hackers
Hi, 

I was wondering why -Os is not used in place of -O2 while compiling the Postgres sources with gcc. I prepared 2 install directories by respectively using -Os and -O2 flags and in the former case it seems to reduce the install footprint by about 1MB or so. Agreed this is not significant for normal systems. But I was wondering if there is a performance reason too for not using -Os.

Regards,

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Prepping to break every past release...
Next
From: Heikki Linnakangas
Date:
Subject: Re: gcc: why optimize for size flag is not the default