From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
---|---|
To: | "PostgreSQL Hackers Mailing List" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: compile warning |
Date: | 2003-10-11 13:57:13 |
Message-ID: | 006801c38fff$92ef13c0$6401a8c0@DUNSLANE |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)dunslane(dot)net>
To: "PostgreSQL Hackers Mailing List" <pgsql-hackers(at)postgresql(dot)org>
Sent: Saturday, October 11, 2003 8:58 AM
Subject: Re: [HACKERS] compile warning
>
> ----- Original Message -----
> From: "Manfred Spraul" <manfred(at)colorfullife(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2003-10-11 14:00:16 | fix for strict-alias warnings |
Previous Message | Bruno Wolff III | 2003-10-11 13:53:08 | Re: pg_ctl reload - is it safe? |