------- Comment #3 from redi at gcc dot gnu dot org 2009-12-04 11:00 ------- Although as I noted in Bug 40297 comment 2 I think that function should also have a memory barrier when m == memory_order_release, which the current code has "by accident" because of this bug ... so arguably it's better that way!
-- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42273
