On Tue, 13 Jan 2015, Andrew MacLeod wrote: > It seems that it should be safe to move back to the original patch, and remove > that error test for using consume on an exchange...
I don't think there should be any such errors, for any of the atomic built-in functions, only warnings (with the model converted to MEMMODEL_SEQ_CST if not valid, just like a non-constant model). This is just like any other invalid function argument of a suitable type: undefined behavior only if the call is executed. http://www.open-std.org/jtc1/sc22/wg14/12553 -- Joseph S. Myers jos...@codesourcery.com