pkg syscall (windows-386), const PROV_EC_ECNRA_FULL ideal-int
pkg syscall (windows-386), const PROV_EC_ECNRA_SIG ideal-int
pkg syscall (windows-386), const PROV_FORTEZZA ideal-int
pkg syscall (windows-386), const PROV_INTEL_SEC ideal-int
pkg syscall (windows-386), const PROV_MS_EXCHANGE ideal-int
pkg syscall (windows-386), const PROV_REPLACE_OWF ideal-int
pkg syscall (windows-386), const PROV_RNG ideal-int

	PINSRW	$4, foo+4(SB), X2

// LTYPERT spec10	{ outcode($1, &$2); }
	JCS	2(PC)
	RETFL	$4

// Was bug: LOOP is a branch instruction.
	JCS	2(PC)
loop:
	LOOP	loop // LOOP

	// Intel pseudonyms for our own renamings.
	PADDD	M2, M1 // PADDL M2, M1
	MOVDQ2Q	X1, M1 // MOVQ X1, M1
	MOVNTDQ	X1, (AX)	// MOVNTO X1, (AX)
	MOVOA	(AX), X1	// MOVO (AX), X1

// Tests for SP indexed addresses.

// For ARM, only R0 through R15 may appear.
// For ARM64, V0 through V31 with arrangement may appear.
//
// For 386/AMD64 register list specifies 4VNNIW-style multi-source operand.
// For range of 4 elements, Intel manual uses "+3" notation, for example:
//
//	VP4DPWSSDS zmm1{k1}{z}, zmm2+3, m128
//
// Given asm line:
//
//	VP4DPWSSDS Z5, [Z10-Z13], (AX)
//

pkg syscall (windows-386), const PROV_EC_ECNRA_FULL = 17
pkg syscall (windows-386), const PROV_EC_ECNRA_SIG = 15
pkg syscall (windows-386), const PROV_FORTEZZA = 4
pkg syscall (windows-386), const PROV_INTEL_SEC = 22
pkg syscall (windows-386), const PROV_MS_EXCHANGE = 5
pkg syscall (windows-386), const PROV_REPLACE_OWF = 23
pkg syscall (windows-386), const PROV_RNG = 21
pkg syscall (windows-386), const PROV_RSA_AES = 24

</p>

<p>
Here follow some descriptions of key Go-specific details for the supported architectures.
</p>

<h3 id="x86">32-bit Intel 386</h3>

<p>
The runtime pointer to the <code>g</code> structure is maintained
through the value of an otherwise unused (as far as Go is concerned) register in the MMU.