#defineBF_ASM0/* 1 */

#defineBF_SCALE1

#elif defined(__x86_64__)|| defined(__alpha__)|| defined(__hppa__)

#elif defined(__x86_64__)|| defined(__hppa__)

#defineBF_ASM0

#defineBF_SCALE1

<para>

In general, <productname>PostgreSQL</productname> can be expected to work on

these CPU architectures: x86, x86_64, PowerPC,

PowerPC 64, S/390, S/390x, Sparc, Sparc 64, ARM, MIPS, MIPSEL,

and PA-RISC. Code support exists for M68K, M32R, and VAX, but these

these CPU architectures: x86, PowerPC, S/390, Sparc, ARM, MIPS, RISC-V,

and PA-RISC, including

big-endian, little-endian, 32-bit, and 64-bit variants where applicable.

Code support exists for M68K, M88K, M32R, and SuperH, but these

architectures are not known to have been tested recently. It is often

possible to build on an unsupported CPU type by configuring with

<option>--disable-spinlocks</option>, but performance will be poor.

</para>

<para>

<productname>PostgreSQL</productname> can be expected to work onthese operating

systems: Linux (all recent distributions), Windows (10 and later),

FreeBSD, OpenBSD, NetBSD, macOS, AIX, andSolaris.

<productname>PostgreSQL</productname> can be expected to work oncurrent

versions of these operating systems: Linux, Windows,

FreeBSD, OpenBSD, NetBSD,DragonFlyBSD,macOS, AIX,Solaris,andillumos.

Other Unix-like systems may also work but are not currently

being tested. In most cases, all CPU architectures supported by

a given operating system will work. Look in

#if defined(__vax__)

typedefunsignedcharslock_t;

#defineTAS(lock) tas(lock)

static __inline__int

tas(volatileslock_t*lock)

{

registerint_res;

__asm__ __volatile__(

:"=&r"(_res),"+m"(*lock)

:"r"(lock)

:"memory");

return_res;

}

#if defined(__mips__)&& !defined(__sgi)/* non-SGI MIPS */