------- Additional Comments From mckinlay at redhat dot com 2004-10-20 20:49 ------- For the memcpy() thing, in the error given we seem to be relocating something to the exact same position. In this case the memcpy() should be harmless. But, maybe it is possible to get real overlapping relocations. Its probably best just to replace the memcpy() with a memmove() here.
I'm not sure the "unitialized conditional move" errors are really bugs. I've seen this a bit when running valgrind on code compiled with recent GCCs ? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18091
