From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
Cc: | "PG Patches" <pgsql-patches(at)postgresql(dot)org>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Subject: | Re: fix for strict-alias warnings |
Date: | 2003-10-13 06:00:37 |
Message-ID: | 7846.1066024837@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
"Andrew Dunstan" <andrew(at)dunslane(dot)net> writes:
> Even without the extra overhead, the danger of strict-aliasing is not just
> related to alignment.
If I understand the issue at all, it has *nothing* to do with alignment.
> As I understand it, given strict-aliasing assumptions
> the compiler is free to reorder some operations on things it thinks can't be
> the same thing, or even optimise them away because they can have no effect.
Yah...
> I'm not 100% sure we have avoided that danger.
I don't think we understand the dangers quite yet, and I think the
patches applied to date constitute useless thrashing rather than fixes.
I'd like to see less quick-hack patching and more discussion.
In particular, given that there is as yet no demonstrated effect other
than mere warnings issued by a possibly-buggy gcc release, I think it's
premature to be hacking our sources at all.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 2003-10-13 06:24:48 | Re: Still not able to initdb |
Previous Message | Andrew Dunstan | 2003-10-13 05:34:21 | Re: fix for strict-alias warnings |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2003-10-13 11:18:16 | Re: [PATCHES] fix for strict-alias warnings |
Previous Message | Andrew Dunstan | 2003-10-13 05:34:21 | Re: fix for strict-alias warnings |