This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc 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: [RFC PATCH v3 05/12] C-SKY: Atomic and Locking Routines

From: Joseph Myers <joseph at codesourcery dot com>
To: Mao Han <han_mao at c-sky dot com>
Cc: <libc-alpha at sourceware dot org>, <c-sky_gcc_upstream at c-sky dot com>, <gnu-csky at mentor dot com>
Date: Fri, 29 Jun 2018 16:36:19 +0000
Subject: Re: [RFC PATCH v3 05/12] C-SKY: Atomic and Locking Routines
References: <cover.1530246556.git.han_mao@c-sky.com> <52862eb735de64be1bd5a61b21ef9585e665558d.1530246556.git.han_mao@c-sky.com>

On Fri, 29 Jun 2018, Mao Han wrote:

> +#define USE_ATOMIC_COMPILER_BUILTINS 0

Does this mean the compiler expands the atomic built-in function calls to 
out-of-line calls to libgcc or libatomic, but you wish to use inline 
expansions in glibc?  (That's the main case when 
USE_ATOMIC_COMPILER_BUILTINS 0 is appropriate.  If there are suitable 
atomic instructions, typically the compiler would expand the calls inline 
and USE_ATOMIC_COMPILER_BUILTINS 1 is most appropriate rather than using 
inline asm for atomics.)

-- 
Joseph S. Myers
joseph@codesourcery.com

References:
- [RFC PATCH v3 00/12] port C-SKY to glibc
  - From: Mao Han
- [RFC PATCH v3 05/12] C-SKY: Atomic and Locking Routines
  - From: Mao Han

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