i386 memory fence incompatible with valgrind

Matthias Urlichs matthias at urlichs.de
Wed Jan 11 08:35:38 CET 2017

On 11.01.2017 08:14, Marc Lehmann wrote:
> The area *is* a legitimate memory location, and I am sure valgrind agrees.
Umm, while it's legitimate to access it, the problem is that it cannot
have any defined content – an interrupt could alter the data stored
there at any time.

Valgrind knows that, thus it complains.
> The instruction is a standard memory fence pattern also used by linux
> for example,
Linux uses 0(%esp). Why are you using an offset of -1? An offset of zero
would fix the problem.

-- Matthias Urlichs

More information about the libev mailing list