Re: Why is it so easy to override -fno-strict-aliasing?

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Why is it so easy to override -fno-strict-aliasing?
Date: 2004-01-30 19:06:05
Message-ID: 401AAB1D.3020208@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

>In config/c-compiler.m4 I read
>
>if test "$ac_env_CFLAGS_set" != set; then
> CFLAGS="$CFLAGS $pgac_cv_prog_cc_no_strict_aliasing"
>fi
>
>This means that a configure operation as innocuous-looking as
>
> CFLAGS="-O3" ./configure
>
>will break the build on gcc >= 3.3 because it will fail to supply
>-fno-strict-aliasing. I claim this is a lousy idea. We should drop
>the if-test and always add -fno-strict-aliasing if the compiler
>will take it. People who *really* know what they are doing can
>experiment with removing the switch from Makefile.global after
>configure, but I don't think it should be quite this easy to lose it.
>
>
>

I agree.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Scott Lamb 2004-01-30 19:57:52 Re: Mixing threaded and non-threaded
Previous Message Tom Lane 2004-01-30 18:49:49 Why is it so easy to override -fno-strict-aliasing?