Re: compile warning - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: compile warning
Date
Msg-id 006801c38fff$92ef13c0$6401a8c0@DUNSLANE
Whole thread Raw
In response to Re: compile warning  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: compile warning
List pgsql-hackers
I have a fix for this which I will post to patches - essentially you cast
the pointers to (void *) and the compiler doesn't complain. It would be a
pity to turn off strict aliasing altogether, as it is known to improve
performance in some cases.

Tested on Cygwin/GCC 3.3.1

cheers

andrew


----- Original Message ----- 
From: "Andrew Dunstan" <andrew@dunslane.net>
To: "PostgreSQL Hackers Mailing List" <pgsql-hackers@postgresql.org>
Sent: Saturday, October 11, 2003 8:58 AM
Subject: Re: [HACKERS] compile warning


>
> ----- Original Message ----- 
> From: "Manfred Spraul" <manfred@colorfullife.com>
> >
> > The kernel is still compiled with -fno-strict-aliasing - I'm not sure if
> > there are outstanding problems, or if it's just a safety precaution.
> >
>
> We should probably do likewise, at least until this is cleaned up, if
that's
> what we want to do, again probably from an overabundance of caution.
>
> cheers
>
> andrew
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>       joining column's datatypes do not match



pgsql-hackers by date:

Previous
From: Bruno Wolff III
Date:
Subject: Re: pg_ctl reload - is it safe?
Next
From: Bruce Momjian
Date:
Subject: Re: compile warning