Ok .. I backed out the bogus casts and took the lazy approach
(-fno-strict-alias). Thanks for the background on this.
J
On Monday 12 November 2007 13:13, Dirk Mueller wrote:
> On Wednesday 07 November 2007, Julian Seward wrote:
> > > a real workaround would be to copy the content into a new loc
On Wednesday 07 November 2007, Julian Seward wrote:
> > a real workaround would be to copy the content into a new location (e.g.
> > a local variable) and access that one via its type.
> I'd like to fix it properly, but there's lots of code like this:
>
>while (TC_(nextIterFM)( map_locks, (Wor
On Wednesday 07 November 2007 00:37, Dirk Mueller wrote:
Dirk, thanks for the info.
> it is not... the only reasonable fix would be to fix that code or
> use -fno-strict-aliasing.
urr. just what I didn't want to hear :-)
> a real workaround would be to copy the content into a new location (e.
On Tuesday 06 November 2007, [EMAIL PROTECTED] wrote:
> +/* Note there are a whole bunch of ugly double casts of the form
> + (Word*)(void*)&p. These placate gcc at -O2. The obvious form
> + (Word*)&p causes gcc to complain that 'dereferencing a type-punned
> + pointer ill break strict-alia
Author: sewardj
Date: 2007-11-06 22:47:45 + (Tue, 06 Nov 2007)
New Revision: 7105
Log:
Build at -O2, and insert lots of ugly casts to stop gcc complaining
about violations of strict aliasing rules. Whether these casts are
really a reasonable "solution" is another matter.
Modified:
branche
