another gcc 4.2 breakage?

[Poul-Henning Kamp]

In message <4716470E.9010101 at FreeBSD.org>, Kris Kennaway writes:

>> I have a compile fix for this problem -- the resulting binary dumps
>> core though. I can commit the fix and mark the port IGNORE on RELENG_7
>> until we have a proper solution.

I don't think a proper solution will happen, until we get a new port
based on more recent valgrind code.

We could use more hands getting all our syscalls implemented in
valgrind, so volunteers are more than welcome help out in

	//depot/projects/valgrind/...

Last I had a couple of days to spend, I got as far as running
thr/umtx based multi-threaded programs.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.