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: Alexander Monakov <amonakov at ispras dot ru>
To: Andrew Haley <aph at redhat dot com>
Cc: Mattias Rönnblom <hofors at lysator dot liu dot se>, gcc at gcc dot gnu dot org
Date: Thu, 19 Oct 2017 15:31:20 +0300 (MSK)
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>

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).

Alexander

Follow-Ups:
- Re: atomic_thread_fence() semantics
  - From: Mattias Rönnblom
- Re: atomic_thread_fence() semantics
  - From: Torvald Riegel

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

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