This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: atomic_thread_fence() semantics

From: Mattias Rönnblom <hofors at lysator dot liu dot se>
To: gcc at gcc dot gnu dot org
Date: Thu, 19 Oct 2017 14:52:26 +0200
Subject: Re: atomic_thread_fence() semantics
Authentication-results: sourceware.org; auth=none
References: <351d54cc-4da1-dd20-aace-17c5b6244e1a@lysator.liu.se> <c5e41c53-ebae-6e8b-f276-9977eff37a5a@redhat.com> <alpine.LNX.2.20.13.1710191529180.21379@monopod.intra.ispras.ru>

On 2017-10-19 14:31, Alexander Monakov wrote:

On Thu, 19 Oct 2017, Andrew Haley wrote:

On 19/10/17 12:58, Mattias Rönnblom wrote:

Did I misunderstand the semantics of
atomic_thread_fence+memory_order_release?


No, you did not.  This looks like a bug.  Please report it.


This bug is fixed on trunk, so should work from gcc-8 onwards (PR 80640).


OK, thanks!

Regards,
	Mattias

References:
- atomic_thread_fence() semantics
  - From: Mattias Rönnblom
- Re: atomic_thread_fence() semantics
  - From: Andrew Haley
- Re: atomic_thread_fence() semantics
  - From: Alexander Monakov

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]