NetBSD/sys/arch/or1k
thorpej 26788c945d - In kern_mutex.c, if MUTEX_CAS() is not defined, define it in terms of
atomic_cas_ulong().
- For arm, ia64, m68k, mips, or1k, riscv, vax: don't define our own
  MUTEX_CAS(), as they either use atomic_cas_ulong() or equivalent
  (atomic_cas_uint() on m68k).
- For alpha and sparc64, don't define MUTEX_CAS() in terms of their own
  _lock_cas(), which has its own memory barriers; the call sites in
  kern_mutex.c already have the appropriate memory barrier calls.  Thus,
  alpha and sparc64 can use default definition.
- For sh3, don't define MUTEX_CAS() in terms of its own _lock_cas();
  atomic_cas_ulong() is strong-aliased to _lock_cas(), therefore defining
  our own MUTEX_CAS() is redundant.

Per thread:
	https://mail-index.netbsd.org/tech-kern/2021/07/25/msg027562.html
2021-08-25 04:13:41 +00:00
..
conf Remove uscanner(4) driver 2021-06-29 10:22:33 +00:00
include - In kern_mutex.c, if MUTEX_CAS() is not defined, define it in terms of 2021-08-25 04:13:41 +00:00
Makefile