From 7380191059399922136 X-Google-Thread: f78e5,4c3ccbaec057287f X-Google-NewGroupId: yes X-Google-Attributes: gid7894ca11fe,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news1.google.com!news.glorb.com!news.alt.net From: Alexander Terekhov Newsgroups: comp.std.c++ Subject: Re: proposal for memory_order_seq_cst constraints Date: Fri, 4 Mar 2011 03:14:31 CST Organization: A noiseless patient Spider Lines: 15 Sender: std-cpp-request@vandevoorde.com Approved: james.dennett@gmail.com Message-ID: <4D6FCB57.43262D16@web.de> References: Reply-To: terekhov@web.de Content-Type: text/plain; charset=us-ascii To: undisclosed-recipients:; Return-Path: X-Original-Date: Thu, 03 Mar 2011 18:09:43 +0100 X-Submission-Address: std-c++-submit@vandevoorde.com Xref: g2news2.google.com comp.std.c++:3171 The rule of thumb is that you should never combine memory_order_seq_cst with more relaxed modes of access. If you do not like memory_order_seq_cst then get rid of memory_order_seq_cst entirely. regards, alexander. -- [ comp.std.c++ is moderated. To submit articles, try posting with your ] [ newsreader. If that fails, use mailto:std-cpp-submit@vandevoorde.com ] [ --- Please see the FAQ before posting. --- ] [ FAQ: http://www.comeaucomputing.com/csc/faq.html ]