On Sat, Apr 13, 2013 at 02:29:00PM +0200, Matthias Moeller <[email protected]>
wrote:
> I'm getting some valgrind hits from libev-4.15. It's always with the
> ECB_MEMORY_FENCE macro. I've checked both AMD64 and i386, the hits
> occur on the i386 version only.
>
> This memory fencing stuff is beyond my knowledge. Is this something
> to worry about?
No, this is just a (harmless) bug in valgrind, which apparently doesn't
recognise the lock prefix correctly, or somesuch.
It doesn't affect correctness inside and outside of valgrind.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / [email protected]
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
libev mailing list
[email protected]
http://lists.schmorp.de/cgi-bin/mailman/listinfo/libev
