Following JF's comment, I updated the clobber list of NoBarrier operations
to
include "memory", and added a comment explaining why.
Tests showed no difference in the code generated between integrating the
barrier
in the inline asm and using a function MemoryBarrier(), so I prefer not
duplicating the assembly code.
https://codereview.chromium.org/220793002/
--
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
