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.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, (Word*)(void*)&gla,
(Word*)(void*)&lk )) {
...
}
and copying two values into a new location would be ugly.
> piece of memory via pointers that have a different type (except for the
> non-symmetrical char* exception). in this case I guess it is because Word*
char* exception? Does the standard say a char* can point at anything?
If yes, can I use the same hack as I just committed, but with char* as
the intermediate type instead of void* ?
J
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Valgrind-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
