Re: Patch - Debug builds without optimization

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Bernd Helmle <mailings(at)oopsware(dot)de>
Cc: Radosław Smogura <rsmogura(at)softperience(dot)eu>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch - Debug builds without optimization
Date: 2011-06-16 17:06:50
Message-ID: 1308243991-sup-8819@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Excerpts from Bernd Helmle's message of jue jun 16 09:37:24 -0400 2011:
>
>
> --On 16. Juni 2011 14:30:27 +0200 Radosław Smogura <rsmogura(at)softperience(dot)eu>
> wrote:
>
> > Hello,
> >
> > I'm sending following patch which disables optimization when --enable-debug
> > is passed. It was nasty (for me, at least) that debug build required passing
> > of CFLAGS with -O0 to get nice traceable code.
>
> -O0 hides bugs in your code (e.g. look at
> <http://archives.postgresql.org/message-id/9714F5232AB2C4FCFCB392D5@amenophis>
> and replies for an example to do it better). Doing this automatically on debug
> builds would be a step backwards.

Hah, seems I don't always do it the same way ;-)

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message A.M. 2011-06-16 17:22:47 Re: POSIX shared memory patch status
Previous Message Alvaro Herrera 2011-06-16 17:02:22 Re: Re: starting to review the Extend NOT NULL representation to pg_constraint patch