https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62642
--- Comment #5 from M8R-ynb11d at mailinator dot com --- I originally put the barriers there in a futile attempt to work around the bug. Can anyone tell me whether I actually need them, or whether the intrinsic carries with it an implicit built-in barrier to prevent reordering? Ideally I'd like to write portable code using only intrinsics and not gcc-specific asm() stuff, so I hope that it's the latter.