From: "Leopold Toetsch" <[EMAIL PROTECTED]> > That isn't necessary. One rmb() after resetting C<str_val> ought to be > enough. It ensures that in all cases the other CPU reads str_val as > NULL. If the vtable is still pointing to the PerlInt vtable, its a user
Having an only rmb() on the writing CPU hardly assures that. http://lse.sourceforge.net/locking/wmbdd.html http://www.ussg.iu.edu/hypermail/linux/kernel/0007.3/0481.html http://www.ussg.iu.edu/hypermail/linux/kernel/0110.1/0409.html > Yep. But don't care: i386 doesn't need these memory barriers. i386 is not the sole CPU architecture which runs windows. 0x4C56
