#### 9.15.17 Specifying CPU Architecture

`as` may be told to assemble for a particular CPU (sub-)architecture with the `.arch` cpu_type directive. This directive enables a warning when gas detects an instruction that is not supported on the CPU specified. The choices for cpu_type are:

‘`i8086`’ | ‘`i186`’ | ‘`i286`’ | ‘`i386`’
‘`i486`’ | ‘`i586`’ | ‘`i686`’ | ‘`pentium`’
‘`pentiumpro`’ | ‘`pentiumii`’ | ‘`pentiumiii`’ | ‘`pentium4`’
‘`prescott`’ | ‘`nocona`’ | ‘`core`’ | ‘`core2`’
‘`corei7`’ | ‘`l1om`’ | ‘`k1om`’
‘`k6`’ | ‘`k6_2`’ | ‘`athlon`’ | ‘`k8`’
‘`amdfam10`’ | ‘`bdver1`’ | ‘`bdver2`’ | ‘`bdver3`’
‘`btver1`’ | ‘`btver2`’
‘`generic32`’ | ‘`generic64`’
‘`.mmx`’ | ‘`.sse`’ | ‘`.sse2`’ | ‘`.sse3`’
‘`.ssse3`’ | ‘`.sse4.1`’ | ‘`.sse4.2`’ | ‘`.sse4`’
‘`.avx`’ | ‘`.vmx`’ | ‘`.smx`’ | ‘`.ept`’
‘`.clflush`’ | ‘`.movbe`’ | ‘`.xsave`’ | ‘`.xsaveopt`’
‘`.aes`’ | ‘`.pclmul`’ | ‘`.fma`’ | ‘`.fsgsbase`’
‘`.rdrnd`’ | ‘`.f16c`’ | ‘`.avx2`’ | ‘`.bmi2`’
‘`.lzcnt`’ | ‘`.invpcid`’ | ‘`.vmfunc`’ | ‘`.hle`’
‘`.rtm`’ | ‘`.adx`’ | ‘`.rdseed`’ | ‘`.prfchw`’
‘`.smap`’ | ‘`.mpx`’
‘`.smap`’ | ‘`.sha`’
‘`.smap`’ | ‘`.clflushopt`’ | ‘`.xsavec`’ | ‘`.xsaves`’
‘`.smap`’ | ‘`.prefetchwt1`’
‘`.3dnow`’ | ‘`.3dnowa`’ | ‘`.sse4a`’ | ‘`.sse5`’
‘`.syscall`’ | ‘`.rdtscp`’ | ‘`.svme`’ | ‘`.abm`’
‘`.lwp`’ | ‘`.fma4`’ | ‘`.xop`’ | ‘`.cx16`’
‘`.padlock`’
‘`.smap`’ | ‘`.avx512f`’ | ‘`.avx512cd`’ | ‘`.avx512er`’
‘`.avx512pf`’ | ‘`.3dnow`’ | ‘`.3dnowa`’ | ‘`.sse4a`’
‘`.sse5`’ | ‘`.syscall`’ | ‘`.rdtscp`’ | ‘`.svme`’
‘`.abm`’ | ‘`.lwp`’ | ‘`.fma4`’ | ‘`.xop`’
‘`.cx16`’ | ‘`.padlock`’

Apart from the warning, there are only two other effects on `as` operation; Firstly, if you specify a CPU other than ‘`i486`’, then shift by one instructions such as ‘`sarl $1, %eax`’ will automatically use a two byte opcode sequence. The larger three byte opcode sequence is used on the 486 (and when no architecture is specified) because it executes faster on the 486. Note that you can explicitly request the two byte opcode by writing ‘`sarl %eax`’. Secondly, if you specify ‘`i8086`’, ‘`i186`’, or ‘`i286`’, and ‘`.code16`’ or ‘`.code16gcc`’ then byte offset conditional jumps will be promoted when necessary to a two instruction sequence consisting of a conditional jump of the opposite sense around an unconditional jump to the target.

Following the CPU architecture (but not a sub-architecture, which are those starting with a dot), you may specify ‘`jumps`’ or ‘`nojumps`’ to control automatic promotion of conditional jumps. ‘`jumps`’ is the default, and enables jump promotion; All external jumps will be of the long variety, and file-local jumps will be promoted as necessary. (see i386-Jumps) ‘`nojumps`’ leaves external conditional jumps as byte offset jumps, and warns about file-local conditional jumps that `as` promotes. Unconditional jumps are treated as for ‘`jumps`’.

For example

          .arch i8086,nojumps