Skip site navigation (1) Skip section navigation (2)

Re: additional GCC warning flags

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>,pgsql-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: additional GCC warning flags
Date: 2004-10-19 16:07:54
Message-ID: 16516.1098202074@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
Neil Conway <neilc(at)samurai(dot)com> writes:
> Attached is a revised patch. Changes:

Looks reasonable to me.  Just one comment: should the
-fno-strict-aliasing probe be inside the "if test "$GCC" = yes" part?
It effectively was in the original.

> BTW, since we're on the topic of compiler options, is there a reason we
> don't use -g3 with GCC when --enable-debug is specified? It seems worth
> using to me.

How much does it bloat the executable?

			regards, tom lane

In response to

Responses

pgsql-patches by date

Next:From: Tom LaneDate: 2004-10-19 16:16:47
Subject: Re: additional GCC warning flags
Previous:From: Andrew DunstanDate: 2004-10-19 15:44:05
Subject: Re: [HACKERS] strange result from contrib/seg regression on windows

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group