AS(1)

๐Ÿ“ฆ version 2.47, in arch rolling

๐Ÿ’… AS(1) ๐Ÿ’…

okay so this is AS(1) from GNU Development Tools โ€” aka the portable GNU assembler. She's iconic, she's lowkey everywhere, and she's here to turn your assembly into object files. Let's get into it, bestie. ๐Ÿซถ


๐ŸŒธ NAME ๐ŸŒธ

AS โ€” the portable GNU assembler.

That's the name. That's the whole vibe. No cap. โœจ


๐ŸŽ€ SYNOPSIS ๐ŸŽ€

bestie, here's the full invocation shape. I'm keeping every bracket and option exactly as-is so nobody's build breaks and blames me:

as [-a[cdghilns][=file]]
 [--alternate]
 [--compress-debug-sections] [--nocompress-debug-sections]
 [-D]
 [--dump-config]
 [--debug-prefix-map old=new]
 [--defsym sym=val]
 [--elf-stt-common=[no|yes]]
 [--emulation=name]
 [-f]
 [-g] [--gstabs] [--gstabs+]
 [--gdwarf-<N>] [--gdwarf-sections]
 [--gdwarf-cie-version=VERSION]
 [--generate-missing-build-notes=[no|yes]]
 [--gsframe] [--gsframe=[no|yes]]
 [--gsframe-3]
 [--hash-size=N]
 [--help] [--target-help]
 [--info] [--no-info]
 [-I dir]
 [-J]
 [-K]
 [--keep-locals]
 [-L]
 [--listing-lhs-width=NUM]
 [--listing-lhs-width2=NUM]
 [--listing-rhs-width=NUM]
 [--listing-cont-lines=NUM]
 [--multibyte-handling=[allow|warn|warn-sym-only]]
 [--no-pad-sections]
 [-o objfile] [-R]
 [--reloc-section-sym=[all|internal|none]]
 [--scfi=experimental]
 [--sectname-subst]
 [--size-check=[error|warning]]
 [--statistics]
 [-v] [--verbose]
 [-version] [--version]
 [-W] [--no-warn] [--warn] [--fatal-warnings]
 [-w] [-x]
 [-Z] [@FILE]
 [target-options]
 [--|files ...]

๐ŸŽฏ TARGET ๐ŸŽฏ

Target-specific options are their own whole multiverse, and I am not about to let one go missing. Here's every target group, with the option strings kept exactly as they should be. ๐Ÿ’–

Target AArch64 options

[-EB|-EL]
[-mabi=ABI]

Target Alpha options

[-mcpu]
[-mdebug | -no-mdebug]
[-replace | -noreplace]
[-relax] [-g] [-Gsize]
[-F] [-32addr]

Target ARC options

[-mcpu=cpu]
[-mA6|-mARC600|-mARC601|-mA7|-mARC700|-mEM|-mHS]
[-mcode-density]
[-mrelax]
[-EB|-EL]

Target ARM options

[-mcpu=processor[+extension...]]
[-march=architecture[+extension...]]
[-mfpu=floating-point-format]
[-mfloat-abi=abi]
[-meabi=ver]
[-mthumb]
[-EB|-EL]
[-mapcs-32|-mapcs-26|-mapcs-float|
 -mapcs-reentrant]
[-mthumb-interwork] [-k]

Target Blackfin options

[-mcpu=processor[-sirevision]]
[-mfdpic]
[-mno-fdpic]
[-mnopic]

Target BPF options

[-EL] [-EB]

Target CRIS options

[--underscore | --no-underscore]
[--pic] [-N]
[--emulation=criself | --emulation=crisaout]
[--march=v0_v10 | --march=v10 | --march=v32 | --march=common_v10_v32]

Target C-SKY options

[-march=arch] [-mcpu=cpu]
[-EL] [-mlittle-endian] [-EB] [-mbig-endian]
[-fpic] [-pic]
[-mljump] [-mno-ljump]
[-force2bsr] [-mforce2bsr] [-no-force2bsr] [-mno-force2bsr]
[-jsri2bsr] [-mjsri2bsr] [-no-jsri2bsr ] [-mno-jsri2bsr]
[-mnolrw ] [-mno-lrw]
[-melrw] [-mno-elrw]
[-mlaf ] [-mliterals-after-func]
[-mno-laf] [-mno-literals-after-func]
[-mlabr] [-mliterals-after-br]
[-mno-labr] [-mnoliterals-after-br]
[-mistack] [-mno-istack]
[-mhard-float] [-mmp] [-mcp] [-mcache]
[-msecurity] [-mtrust]
[-mdsp] [-medsp] [-mvdsp]

Target D10V options

[-O]

Target D30V options

[-O|-n|-N]

Target EPIPHANY options

[-mepiphany|-mepiphany16]

Target H8/300 options

[-h-tick-hex]

Target i386 options

[--32|--x32|--64] [-n]
[-march=CPU[+EXTENSION...]] [-mtune=CPU]

Target IA-64 options

[-mconstant-gp|-mauto-pic]
[-milp32|-milp64|-mlp64|-mp64]
[-mle|mbe]
[-mtune=itanium1|-mtune=itanium2]
[-munwind-check=warning|-munwind-check=error]
[-mhint.b=ok|-mhint.b=warning|-mhint.b=error]
[-x|-xexplicit] [-xauto] [-xdebug]

Target IP2K options

[-mip2022|-mip2022ext]

Target M32C options

[-m32c|-m16c] [-relax] [-h-tick-hex]

Target M32R options

[--m32rx|--[no-]warn-explicit-parallel-conflicts|
--W[n]p]

Target M680X0 options

[-l] [-m68000|-m68010|-m68020|...]

Target M68HC11 options

[-m68hc11|-m68hc12|-m68hcs12|-mm9s12x|-mm9s12xg]
[-mshort|-mlong]
[-mshort-double|-mlong-double]
[--force-long-branches] [--short-branches]
[--strict-direct-mode] [--print-insn-syntax]
[--print-opcodes] [--generate-example]

Target MCORE options

[-jsri2bsr] [-sifilter] [-relax]
[-mcpu=[210|340]]

Target Meta options

[-mcpu=cpu] [-mfpu=cpu] [-mdsp=cpu]

Target MICROBLAZE options

[-mlittle-endian] [-mbig-endian]

Target MIPS options

[-nocpp] [-EL] [-EB] [-O[optimization level]]
[-g[debug level]] [-G num] [-KPIC] [-call_shared]
[-non_shared] [-xgot [-mvxworks-pic]
[-mabi=ABI] [-32] [-n32] [-64] [-mfp32] [-mgp32]
[-mfp64] [-mgp64] [-mfpxx]
[-modd-spreg] [-mno-odd-spreg]
[-march=CPU] [-mtune=CPU] [-mips1] [-mips2]
[-mips3] [-mips4] [-mips5] [-mips32] [-mips32r2]
[-mips32r3] [-mips32r5] [-mips32r6] [-mips64] [-mips64r2]
[-mips64r3] [-mips64r5] [-mips64r6]
[-construct-floats] [-no-construct-floats]
[-mignore-branch-isa] [-mno-ignore-branch-isa]
[-mnan=encoding]
[-trap] [-no-break] [-break] [-no-trap]
[-mips16] [-no-mips16]
[-mmips16e2] [-mno-mips16e2]
[-mmicromips] [-mno-micromips]
[-msmartmips] [-mno-smartmips]
[-mips3d] [-no-mips3d]
[-mdmx] [-no-mdmx]
[-mdsp] [-mno-dsp]
[-mdspr2] [-mno-dspr2]
[-mdspr3] [-mno-dspr3]
[-mmsa] [-mno-msa]
[-mxpa] [-mno-xpa]
[-mmt] [-mno-mt]
[-mmcu] [-mno-mcu]
[-mcrc] [-mno-crc]
[-mginv] [-mno-ginv]
[-mloongson-mmi] [-mno-loongson-mmi]
[-mloongson-cam] [-mno-loongson-cam]
[-mloongson-ext] [-mno-loongson-ext]
[-mloongson-ext2] [-mno-loongson-ext2]
[-minsn32] [-mno-insn32]
[-mfix7000] [-mno-fix7000]
[-mfix-rm7000] [-mno-fix-rm7000]
[-mfix-vr4120] [-mno-fix-vr4120]
[-mfix-vr4130] [-mno-fix-vr4130]
[-mfix-r5900] [-mno-fix-r5900]
[-mdebug] [-no-mdebug]
[-mpdr] [-mno-pdr]

Target MMIX options

[--fixed-special-register-names] [--globalize-symbols]
[--gnu-syntax] [--relax] [--no-predefined-symbols]
[--no-expand] [--no-merge-gregs] [-x]
[--linker-allocated-gregs]

Target NDS32 options

[-EL] [-EB] [-O] [-Os] [-mcpu=cpu]
[-misa=isa] [-mabi=abi] [-mall-ext]
[-m[no-]16-bit]  [-m[no-]perf-ext] [-m[no-]perf2-ext]
[-m[no-]string-ext] [-m[no-]dsp-ext] [-m[no-]mac] [-m[no-]div]
[-m[no-]audio-isa-ext] [-m[no-]fpu-sp-ext] [-m[no-]fpu-dp-ext]
[-m[no-]fpu-fma] [-mfpu-freg=FREG] [-mreduced-regs]
[-mfull-regs] [-m[no-]dx-regs] [-mpic] [-mno-relax]
[-mb2bb]

Target PDP11 options

[-mpic|-mno-pic] [-mall] [-mno-extensions]
[-mextension|-mno-extension]
[-mcpu] [-mmachine]

Target picoJava options

[-mb|-me]

Target PowerPC options

[-a32|-a64]
[-mpwrx|-mpwr2|-mpwr|-m601|-mppc|-mppc32|-m603|-m604|-m403|-m405|
 -m440|-m464|-m476|-m7400|-m7410|-m7450|-m7455|-m750cl|-mgekko|
 -mbroadway|-mppc64|-m620|-me500|-e500x2|-me500mc|-me500mc64|-me5500|
 -me6500|-mppc64bridge|-mbooke|-mpower4|-mpwr4|-mpower5|-mpwr5|-mpwr5x|
 -mpower6|-mpwr6|-mpower7|-mpwr7|-mpower8|-mpwr8|-mpower9|-mpwr9-ma2|
 -mcell|-mspe|-mspe2|-mtitan|-me300|-mcom]
[-many] [-maltivec|-mvsx|-mhtm|-mvle]
[-mregnames|-mno-regnames]
[-mrelocatable|-mrelocatable-lib|-K PIC] [-memb]
[-mlittle|-mlittle-endian|-le|-mbig|-mbig-endian|-be]
[-nops=count]

Target PRU options

[-link-relax]
[-mnolink-relax]
[-mno-warn-regname-label]

Target RISC-V options

[-fpic|-fPIC|-fno-pic]
[-march=ISA|Profiles|Profiles_ISA]
[-mabi=ABI]
[-mlittle-endian|-mbig-endian]

Target RL78 options

[-mg10]
[-m32bit-doubles|-m64bit-doubles]

Target RX options

[-mlittle-endian|-mbig-endian]
[-m32bit-doubles|-m64bit-doubles]
[-muse-conventional-section-names]
[-msmall-data-limit]
[-mpid]
[-mrelax]
[-mint-register=number]
[-mgcc-abi|-mrx-abi]

Target s390 options

[-m31|-m64] [-mesa|-mzarch] [-march=CPU]
[-mregnames|-mno-regnames]
[-mwarn-areg-zero]
[-mwarn-regtype-mismatch=strict
 -mwarn-regtype-mismatch=relaxed
 -mwarn-regtype-mismatch=no
 -mno-warn-regtype-mismatch]

Target SCORE options

[-EB][-EL][-FIXDD][-NWARN]
[-SCORE5][-SCORE5U][-SCORE7][-SCORE3]
[-march=score7][-march=score3]
[-USE_R1][-KPIC][-O0][-G num][-V]

Target SPARC options

[-Av6|-Av7|-Av8|-Aleon|-Asparclet|-Asparclite
 -Av8plus|-Av8plusa|-Av8plusb|-Av8plusc|-Av8plusd
 -Av8plusv|-Av8plusm|-Av9|-Av9a|-Av9b|-Av9c
 -Av9d|-Av9e|-Av9v|-Av9m|-Asparc|-Asparcvis
 -Asparcvis2|-Asparcfmaf|-Asparcima|-Asparcvis3
 -Asparcvisr|-Asparc5]
[-xarch=v8plus|-xarch=v8plusa]|-xarch=v8plusb|-xarch=v8plusc
 -xarch=v8plusd|-xarch=v8plusv|-xarch=v8plusm|-xarch=v9
 -xarch=v9a|-xarch=v9b|-xarch=v9c|-xarch=v9d|-xarch=v9e
 -xarch=v9v|-xarch=v9m|-xarch=sparc|-xarch=sparcvis
 -xarch=sparcvis2|-xarch=sparcfmaf|-xarch=sparcima
 -xarch=sparcvis3|-xarch=sparcvisr|-xarch=sparc5
 -bump]
[-32|-64]
[--enforce-aligned-data][--dcti-couples-detect]

Target TIC54X options

[-mcpu=54[123589]|-mcpu=54[56]lp] [-mfar-mode|-mf]
[-merrors-to-file <filename>|-me <filename>]

Target TIC6X options

[-march=arch] [-mbig-endian|-mlittle-endian]
[-mdsbt|-mno-dsbt] [-mpid=no|-mpid=near|-mpid=far]
[-mpic|-mno-pic]

Target TILE-Gx options

[-m32|-m64][-EB][-EL]

Target Visium options

[-mtune=arch]

Target Xtensa options

[--[no-]text-section-literals] [--[no-]auto-litpools]
[--[no-]absolute-literals]
[--[no-]target-align] [--[no-]longcalls]
[--[no-]transform]
[--rename-section oldname=newname]
[--[no-]trampolines]
[--abi-windowed|--abi-call0]

Target Z80 options

[-march=CPU[-EXT][+EXT]]
[-local-prefix=PREFIX]
[-colonless]
[-sdcc]
[-fp-s=FORMAT]
[-fp-d=FORMAT]

โœจ DESCRIPTION โœจ

okay so bestie, plot twist: GNU as isn't just one assembler, it's literally a whole family of assemblers ๐Ÿ’…. If you've used the GNU assembler on one architecture, the vibe on another architecture will feel super familiar โ€” like switching group chats but everyone still uses the same emojis. Every version shares a ton with the others, including object file formats, most assembler directives (which the cool kids call pseudo-ops), and the assembler syntax itself. ๐Ÿซถ

The main character energy of as is assembling the output of the GNU C compiler gcc so the linker ld can do its thing. But ngl, the goal is bigger than that: they've tried to make as assemble correctly everything that other assemblers for the same machine would assemble. Any exceptions? They're documented explicitly, no cap. That said โ€” and this is the important bit โ€” it does not mean as always uses the same syntax as some other assembler for the same architecture. Like, we literally know of several mutually incompatible versions of 680x0 assembly language syntax ๐Ÿ’€.

Every single time you run as, it assembles exactly one source program. That source program is made up of one or more files. (And yes, standard input totally counts as a file, bestie.)

You hand as a command line with zero or more input file names, and the input files get read from left file name to right. Any command-line argument (in any position) that doesn't have some special meaning? Congrats, it's an input file name now ๐ŸŒธ.

If you give as no file names at all, it tries to read one input file from as standard input โ€” which is normally your terminal, bestie ๐Ÿ˜ญ. You may have to type ctl-D to tell as there's no more program left to assemble.

Use -- if you need to explicitly name the standard input file in your command line. (Yes, that's the move ๐Ÿ‘‘.)

If the source is empty, as produces a small, empty object file. Tiny. Iconic. Minimalist. ๐ŸŽ€

as may write warnings and error messages to the standard error file (usually your terminal). This should not happen when a compiler runs as automatically, jsyk. Here's the difference: warnings report an assumption that was made so as could keep assembling a flawed program (it's trying its best, okay ๐Ÿ˜ญ), while errors report a grave problem that stops the assembly. Periodt.

If you're invoking as via the GNU C compiler, you can use the -Wa option to pass arguments through to the assembler. Those assembler arguments have to be separated from each other (and from -Wa) by commas. Example time:

gcc -c -g -O -Wa,-alh,-L file.c

That passes two options to the assembler: -alh (emit a listing to standard output with high-level and assembly source) and -L (retain internal symbols in the symbol table). Slay.

Usually though? You do not need to use this -Wa mechanism, because many compiler command-line options are automatically passed to the assembler by the compiler. (And if you're nosy, you can call the GNU compiler driver with the -v option to see precisely what options it passes to each compilation pass, including the assembler. Detective mode ๐Ÿ”.)


โœจ OPTIONS โœจ

  • @file โ€” read command-line options from file. The options that get read are inserted in place of the original @file option. If file doesn't exist, or can't be read, then the option is treated literally and not removed ๐Ÿ™ˆ.

Options inside file are separated by whitespace. A whitespace character can be included in an option by surrounding the entire option in either single or double quotes. Any character (including a backslash) can be included by prefixing the character you want with a backslash. And the file may itself contain additional @file options โ€” any of those get processed recursively. It's giving inception ๐ŸŒ€.

  • -a[cdghilmns] โ€” turn on listings, in any of a variety of ways:
    • -ac โ€” omit false conditionals
    • -ad โ€” omit debugging directives
    • -ag โ€” include general information, like as version and options passed
    • -ah โ€” include high-level source
    • -al โ€” include assembly
    • -ali โ€” include assembly with ginsn
    • -am โ€” include macro expansions
    • -an โ€” omit forms processing
    • -as โ€” include symbols
    • =file โ€” set the name of the listing file

You can combine these options; for example, use -aln for an assembly listing without forms processing. The =file option, if you use it, must be the last one. By itself, -a defaults to -ahls. ๐Ÿ’–

  • --alternate โ€” begin in alternate macro mode.
  • --compress-debug-sections โ€” compress DWARF debug sections using zlib with SHF_COMPRESSED from the ELF ABI. Heads up: the resulting object file may not be compatible with older linkers and object file utilities โš ๏ธ. Also note โ€” if compression would make a given section larger, then it is not compressed.
  • --compress-debug-sections=none
  • --compress-debug-sections=zlib
  • --compress-debug-sections=zlib-gnu
  • --compress-debug-sections=zlib-gabi
  • --compress-debug-sections=zstd โ€” these options control how DWARF debug sections get compressed:
    • --compress-debug-sections=none is equivalent to --nocompress-debug-sections.
    • --compress-debug-sections=zlib and --compress-debug-sections=zlib-gabi are equivalent to --compress-debug-sections.
    • --compress-debug-sections=zlib-gnu compresses DWARF debug sections using the obsoleted zlib-gnu format (vintage, but not in the cute way ๐Ÿ‘€). The debug sections get renamed to begin with .zdebug.
    • --compress-debug-sections=zstd compresses DWARF debug sections using zstd.

Note โ€” if compression would actually make a section larger, then it is neither compressed nor renamed. The assembler is not about to make your file bigger for the aesthetic ๐Ÿ’….

  • --nocompress-debug-sections โ€” do not compress DWARF debug sections. This is usually the default for all targets except the x86/x86_64, but a configure time option can be used to override this.
  • -D โ€” enable debugging in target specific backends, if supported. Otherwise it's just ignored. And even when it's ignored, this option is still accepted for script compatibility with calls to other assemblers. (It's showing up to the party whether or not it gets let in ๐Ÿซถ.)
  • --debug-prefix-map old=new โ€” when assembling files in directory old, record debugging information describing them as in new instead.
  • --defsym sym=value โ€” define the symbol sym to be value before assembling the input file. value must be an integer constant. As in C, a leading 0x indicates a hexadecimal value, and a leading 0 indicates an octal value. The value of the symbol can be overridden inside a source file via the use of a .set pseudo-op.
  • --dump-config โ€” displays how the assembler is configured and then exits. Peek behind the curtain, bestie โœจ.
  • --elf-stt-common=no
  • --elf-stt-common=yes โ€” these options control whether the ELF assembler should generate common symbols with the STT_COMMON type. The default can be controlled by a configure option --enable-elf-stt-common.
  • --emit-local-absolute โ€” emit even pre-defined (local) absolute symbols to the outgoing symbol table. Note that this isn't the exact opposite of --strip-local-absolute ๐Ÿ‘€.
  • --emulation=name โ€” if the assembler is configured to support multiple different target configurations, then this option can be used to select the desired form.
  • -f โ€” "fast" โ€” skip whitespace and comment preprocessing (assume source is compiler output). Zoom zoom ๐Ÿ”ฅ.
  • -g
  • --gen-debug โ€” generate debugging information for each assembler source line using whichever debug format the target prefers. This currently means either STABS, ECOFF or DWARF2. When the debug format is DWARF then a .debug_info and .debug_line section is only emitted when the assembly file doesn't generate one itself.
  • --gstabs โ€” generate stabs debugging information for each assembler line. This may help debugging assembler code, if the debugger can handle it.
  • --gstabs+ โ€” generate stabs debugging information for each assembler line, with GNU extensions that probably only gdb can handle, and that could make other debuggers crash or refuse to read your program ๐Ÿ˜ญ. This may help debugging assembler code. Currently the only GNU extension is the location of the current working directory at assembling time.
  • --gdwarf-2 โ€” generate DWARF2 debugging information for each assembler line. This may help debugging assembler code, if the debugger can handle it. Note โ€” this option is only supported by some targets, not all of them ๐Ÿ™ˆ.
  • --gdwarf-3 โ€” same as the --gdwarf-2 option, except it allows for the possibility of generating extra debug information as per version 3 of the DWARF specification. Note โ€” enabling this option does not guarantee the generation of any extra information; the choice to do so is on a per target basis.
  • --gdwarf-4 โ€” same as the --gdwarf-2 option, except it allows for the possibility of generating extra debug information as per version 4 of the DWARF specification. Note โ€” enabling this option does not guarantee the generation of any extra information; the choice to do so is on a per target basis.
  • --gdwarf-5 โ€” same as the --gdwarf-2 option, except it allows for the possibility of generating extra debug information as per version 5 of the DWARF specification. Note โ€” enabling this option does not guarantee the generation of any extra information; the choice to do so is on a per target basis.
  • --gdwarf-sections โ€” instead of creating a .debug_line section, create a series of .debug_line.foo sections where foo is the name of the corresponding code section. For example, a code section called .text.func will have its dwarf line number information placed into a section called .debug_line.text.func. If the code section is just called .text then the debug line section will still just be called .debug_line without any suffix. Consistent, we love to see it ๐Ÿ’….
  • --gdwarf-cie-version=version โ€” control which version of DWARF Common Information Entries (CIEs) get produced. When this flag isn't specified the default is version 1, though some targets can modify this default. Other possible values for version are 3 or 4.
  • --generate-missing-build-notes=yes
  • --generate-missing-build-notes=no โ€” these options control whether the ELF assembler should generate GNU Build attribute notes if none are present in the input sources. The default can be controlled by the --enable-generate-build-notes configure option.
  • --gsframe
  • --gsframe
  • --gsframe=no
  • --gsframe=yes โ€” create a .sframe section from CFI directives. The explicit --gsframe=yes option behaves the same as --gsframe. Generation can be suppressed with --gsframe=no. The default can be controlled by a configure option --enable-default-sframe. The current version of the emitted SFrame stack trace data is SFRAME_VERSION_3. ๐Ÿฆ‹
  • --gsframe-3 โ€” generate SFrame stack trace information as per Version 3 of the specification.
  • --hash-size N โ€” ignored. Supported for command line compatibility with other assemblers. (It's literally just there to be polite ๐ŸŽ€.)
  • --help โ€” print a summary of the command-line options and exit.
  • --target-help โ€” drops a lil summary of every target-specific option and then dips. that's it, that's the whole job ๐Ÿ’…
  • --info โ€” do NOT suppress the informational messages bestie, let them speak ๐Ÿ—ฃ๏ธ
  • --no-info โ€” okay actually, suppress the informational messages. shhh ๐Ÿคซ
  • -I dir โ€” adds dir to the search list for .include directives. like a little treasure map for includes ๐Ÿ—บ๏ธ
  • -J โ€” do not warn about signed overflow. no thoughts, no warnings โœจ
  • -K โ€” issues warnings when difference tables get altered for long displacements. it's giving "heads up, something moved" ๐Ÿšจ
  • -L, --keep-locals โ€” keeps internal symbols in the symbol table. these symbols start with system-specific local label prefixes, typically .L for ELF systems or L for traditional a.out systems. protect the locals at all costs ๐Ÿซถ
  • --listing-lhs-width=number โ€” sets the max width (in words) of the output data column for an assembler listing to number. measure twice ๐Ÿ“
  • --listing-lhs-width2=number โ€” same energy but for the continuation lines in an assembler listing โ€” max width in words = number ๐Ÿ’ซ
  • --listing-rhs-width=number โ€” sets the max width of an input source line, as displayed in a listing, to number bytes. yes, bytes, not vibes ๐Ÿงš
  • --listing-cont-lines=number โ€” sets the maximum number of lines printed in a listing for a single line of input to number + 1. the +1 is doing the most, honestly ๐Ÿ˜ญ
  • --multibyte-handling=allow, --multibyte-handling=warn, --multibyte-handling=warn-sym-only, --multibyte-handling=warn_sym_only โ€” controls how the assembler handles multibyte characters in the input, and the lore is:
    • the default is to allow such characters without complaint (and you can restore that default by using the allow argument) ๐Ÿ˜Œ
    • the warn argument makes the assembler generate a warning message whenever any multibyte character is encountered ๐Ÿ””
    • the warn-sym-only argument only causes a warning when a symbol is defined with a name that contains multibyte characters. references to undefined symbols will not generate a warning. very "only the main characters get flagged" of it ๐Ÿ‘‘
  • --no-pad-sections โ€” stops the assembler from padding the ends of output sections to the alignment of that section. the default is to pad the sections, but heads up: that can waste space, which might be needed on targets with tight memory constraints ๐Ÿ‘€
  • -o objfile โ€” names the object-file output from as objfile. name your child ๐Ÿผ
  • -R โ€” folds the data section into the text section. merging, combining, becoming one ๐Ÿ”ฅ
  • --reduce-memory-overheads โ€” ignored. it's only there for compatibility with tools that pass the same option to both the assembler and the linker. it's giving "i'm just here so i won't get fined" ๐Ÿ’€
  • --reloc-section-sym=all, --reloc-section-sym=internal, --reloc-section-sym=none โ€” controls whether relocations referencing local binding symbols get adjusted to use section symbols instead. the breakdown:
    • all (the default) โ†’ relocations against all eligible local binding symbols are converted ๐ŸŽ€
    • internal โ†’ only relocations against internal labels (symbols matching the .L prefix) are converted ๐Ÿฆ‹
    • none โ†’ no such conversions are performed. periodt ๐Ÿšซ
  • --scfi=experimental โ€” controls whether the assembler should synthesize CFI for hand-written input. if the input already contains some synthesizable CFI directives, the assembler ignores them and emits a warning. also, --scfi=experimental is not intended to be used for compiler-generated code, including inline assembly โ€” that's a real caveat bestie, listen to it ๐Ÿ™ˆ. this experimental support is work in progress, and only System V AMD64 ABI is supported.

each input function in assembly must begin with the .type directive, and should ideally be closed off using a .size directive. when using SCFI, each .type directive prompts GAS to start a new FDE (a.k.a., Function Descriptor Entry). this implies that with each .type directive, a previous block of instructions, if any, is finalised as a distinct FDE. lots of finalising happening, iconic behavior honestly ๐Ÿ‘‘

  • --sectname-subst โ€” honors substitution sequences in section names. respect the substitutions โœจ
  • --size-check=error, --size-check=warning โ€” issue an error or a warning for an invalid ELF .size directive. pick your fighter ๐Ÿ˜ค
  • --statistics โ€” prints the maximum space (in bytes) and total time (in seconds) used by assembly. the receipts ๐Ÿ“Š
  • --strip-local-absolute โ€” removes local absolute symbols from the outgoing symbol table. bye bestie ๐Ÿ‘‹
  • -v, --verbose โ€” prints the as version. casual little flex ๐Ÿ’โ€โ™€๏ธ
  • --version, -version โ€” prints the as version and exits. no further business, we're done here ๐ŸŽฌ
  • -W, --no-warn โ€” suppresses warning messages. living in denial, but make it a flag ๐Ÿ™ˆ
  • --warn โ€” don't suppress warning messages or treat them as errors. we're listening, respectfully ๐Ÿ‘‚
  • --fatal-warnings โ€” treat warnings as errors. no chill, only consequences ๐Ÿ’€
  • -w โ€” ignored. it's just there. a vibe in the option list ๐Ÿซ 
  • -x โ€” ignored. matching energy with -w ๐Ÿ’ซ
  • -Z โ€” generates an object file even after errors. chaotic but productive ๐Ÿ”ฅ
  • -- files ... โ€” standard input, or source files to assemble. the -- said "everything after this is a file, don't @ me" ๐Ÿ“

๐ŸŒธ so like, the following options are available when as is configured for the 64-bit mode of the ARM Architecture (AArch64). buckle up babygirl, there are a LOT ๐Ÿ’…

  • -EB โ€” specifies that the output generated by the assembler should be marked as being encoded for a big-endian processor. big-endian stans rise ๐Ÿซถ
  • -EL โ€” specifies that the output generated by the assembler should be marked as being encoded for a little-endian processor. little-endian girlies, this one's for you ๐ŸŽ€
  • -mabi=abi โ€” specifies which ABI the source code uses. the recognized arguments are ilp32 and lp64, which decide the generated object file in ELF32 and ELF64 format respectively. the default is lp64. choose wisely ๐Ÿ‘‘
  • -mcpu=processor[+extension...] โ€” specifies the target processor. the assembler will issue an error message if an attempt is made to assemble an instruction which will not execute on the target processor. here's the guest list of recognized processor names: cortex-a34, cortex-a35, cortex-a53, cortex-a55, cortex-a57, cortex-a65, cortex-a65ae, cortex-a72, cortex-a73, cortex-a75, cortex-a76, cortex-a76ae, cortex-a77, cortex-a78, cortex-a78ae, cortex-a78c, cortex-a510, cortex-a520, cortex-a710, cortex-a720, ares, exynos-m1, falkor, neoverse-n1, neoverse-n2, neoverse-e1, neoverse-v1, qdf24xx, saphira, thunderx, vulcan, xgene1 xgene2, cortex-r82, cortex-x1, cortex-x2, cortex-x3, cortex-x4. and the special name all may be used to let the assembler accept instructions valid for any supported processor, including all optional extensions. it's giving "accept everyone" ๐ŸŒˆ

in addition to the basic instruction set, the assembler can be told to accept, or restrict, various extension mnemonics that extend the processor.

if some implementations of a particular processor can have an extension, then those extensions are automatically enabled. consequently, you will not normally have to specify any additional extensions. the assembler's got you ๐Ÿ˜Œ

  • -march=architecture[+extension...] โ€” specifies the target architecture. again, the assembler will issue an error message if you try to assemble an instruction which will not execute on the target architecture. recognized architecture names: armv8-a, armv8.1-a, armv8.2-a, armv8.3-a, armv8.4-a armv8.5-a, armv8.6-a, armv8.7-a, armv8.8-a, armv8.9-a, armv8-r, armv9-a, armv9.1-a, armv9.2-a, armv9.3-a, armv9.4-a and armv9.5-a. the whole family tree ๐ŸŒณ

if both -mcpu and -march are specified, the assembler will use the setting for -mcpu. if neither are specified, the assembler will default to -mcpu=all. -mcpu wins the argument, every time ๐Ÿ˜ค

the architecture option can be extended with the same instruction set extension options as the -mcpu option. but unlike -mcpu, extensions are not always enabled by default. read that again bestie ๐Ÿ‘€

  • -mbig-obj โ€” on PE/COFF target this option forces the use of big object file format, which allows more than 32768 sections. that's a LOT of sections, slay ๐Ÿ’…
  • -mverbose-error โ€” enables verbose error messages for AArch64 gas. this option is enabled by default, so like, you're already living that life โœจ
  • -mno-verbose-error โ€” disables verbose error messages in AArch64 gas. minimalism era ๐Ÿคซ
  • -menable-sysreg-checking โ€” enables error messages that are issued if an attempt is made to assemble a system register access which will not execute on the target architecture. it's a vibe check for your system registers ๐Ÿ‘‘

๐Ÿ“ the following options are available when as is configured for an Alpha processor. throwback era, we respect it ๐Ÿ’œ

  • -mcpu โ€” specifies the target processor. if an attempt is made to assemble an instruction which will not execute on the target processor, the assembler may either expand the instruction as a macro or issue an error message. this option is equivalent to the .arch directive.

the recognized processor names: 21064, 21064a, 21066, 21068, 21164, 21164a, 21164pc, 21264, 21264a, 21264b, ev4, ev5, lca45, ev5, ev56, pca56, ev6, ev67, ev68. and the special name all may be used to allow the assembler to accept instructions valid for any Alpha processor. yes, ev5 is listed twice, we don't talk about it ๐Ÿ’€

in order to support existing practice in OSF/1 with respect to .arch, and existing practice within MILO (the Linux ARC bootloader), the numbered processor names (e.g. 21064) enable the processor-specific PALcode instructions, while the "electro-vlasic" names (e.g. ev4) do not. history lesson over, periodt ๐Ÿ“š

  • -mdebug, -no-mdebug โ€” enables or disables the generation of .mdebug encapsulation for stabs directives and procedure descriptors. the default is to automatically enable .mdebug when the first stabs directive is seen. it just knows ๐Ÿงš
  • -relax โ€” forces all relocations to be put into the object file, instead of saving space and resolving some relocations at assembly time. heads up though: this option does not propagate all symbol arithmetic into the object file, because not all symbol arithmetic can be represented. the option can still be useful in specific applications tho ๐Ÿซถ
  • -replace, -noreplace โ€” enables or disables the optimization of procedure calls, both at assemblage and at link time. these options are only available for VMS targets, and -replace is the default. see section 1.4.1 of the OpenVMS Linker Utility Manual. homework assigned ๐Ÿ“–
  • -g โ€” this option is used when the compiler generates debug information. when gcc is using mips-tfile to generate debug information for ECOFF, local labels must be passed through to the object file. otherwise this option has no effect. situational icon ๐Ÿ’…
  • -Gsize โ€” a local common symbol larger than size is placed in .bss, while smaller symbols are placed in .sbss. size-based sorting, we love an organizational queen ๐Ÿ“ฆ
  • -F, -32addr โ€” these options are ignored for backward compatibility. relics. we keep them for the lore ๐Ÿบ

๐Ÿฆ‹ the following options are available when as is configured for an ARC processor.

  • -mcpu=cpu โ€” selects the core processor variant. short and sweet ๐ŸŽ€
  • -EB | -EL โ€” selects either big-endian (-EB) or little-endian (-EL) output. pick a lane, bestie ๐ŸŒ—
  • -mcode-density โ€” enables Code Density extension instructions. density! compact! efficient! we stan ๐Ÿ”ฅ

๐Ÿ’… ARM, bestie โ€” the processor-family tea

These ones show up when as is built for the ARM processor family:

  • -mcpu=processor[+extension...] โ€” tells it which ARM processor variant you're targeting. Periodt.
  • -march=architecture[+extension...] โ€” says which ARM architecture variant the target is rocking.
  • -mfpu=floating-point-format โ€” picks which Floating Point architecture is the target โœจ
  • -mfloat-abi=abi โ€” picks which floating point ABI is in use.
  • -mthumb โ€” turns on Thumb only instruction decoding. No ARM mixing, we're committed.
  • -mapcs-32 / -mapcs-26 / -mapcs-float / -mapcs-reentrant โ€” picks which procedure calling convention is in use. Choose your fighter ๐Ÿซถ
  • -EB / -EL โ€” selects big-endian (-EB) or little-endian (-EL) output.
  • -mthumb-interwork โ€” says the code was generated with interworking between Thumb and ARM code in mind. It's giving bilingual icon.
  • -mccs โ€” turns on CodeComposer Studio assembly syntax compatibility mode.
  • -k โ€” says PIC code has been generated.

๐Ÿ–ค Blackfin family

These ones pop up when as is configured for the Blackfin processor family:

  • -mcpu=processor[-sirevision] โ€” specifies the target processor. The optional sirevision is not used in the assembler โ€” it's literally just hanging out there so GCC can easily pass down its -mcpu= option. The assembler will throw an error message if you try to assemble an instruction that won't execute on the target processor. The recognized processor names are: bf504, bf506, bf512, bf514, bf516, bf518, bf522, bf523, bf524, bf525, bf526, bf527, bf531, bf532, bf533, bf534, bf535 (not implemented yet ๐Ÿ™ˆ), bf536, bf537, bf538, bf539, bf542, bf542m, bf544, bf544m, bf547, bf547m, bf548, bf548m, bf549, bf549m, bf561, and bf592.
  • -mfdpic โ€” assemble for the FDPIC ABI.
  • -mno-fdpic / -mnopic โ€” disables -mfdpic.

๐Ÿงš BPF (Linux kernel vibes)

These ones are for when as is configured for the Linux kernel BPF processor family. (Yes, the original really does drop a texinfo chapter line right here, so here it is in all its glory:)

@chapter BPF Dependent Features

BPF Options

  • -EB โ€” says the assembler should emit big-endian eBPF.
  • -EL โ€” says the assembler should emit little-endian eBPF.
  • -mdialect=dialect โ€” specifies the assembly language dialect to recognize while assembling. The assembler supports normal and pseudoc.
  • -misa-spec=spec โ€” specifies the version of the BPF instruction set to use when assembling. The supported BPF ISA versions are v1 v2, v3 and v4.

The value xbpf can be specified to recognize extra instructions that are used by GCC for testing purposes. But beware, this is not valid BPF. ๐Ÿ’€

  • -mno-relax โ€” tells the assembler not to relax instructions.
Heads up bestie: if no endianness option is specified on the command line, the host endianness is used. See the info pages for documentation of the CRIS-specific options.

๐Ÿฆ‹ C-SKY cuteness

These ones are available when as is configured for the C-SKY processor family:

  • -march=archname โ€” assemble for architecture archname. The --help option lists valid values for archname.
  • -mcpu=cpuname โ€” assemble for architecture cpuname. The --help option lists valid values for cpuname. (Yes, both say "architecture" โ€” that's what the page says, don't come for me ๐Ÿซถ)
  • -EL / -mlittle-endian โ€” generate little-endian output.
  • -EB / -mbig-endian โ€” generate big-endian output.
  • -fpic / -pic โ€” generate position-independent code.
  • -mljump / -mno-ljump โ€” enable/disable transformation of the short branch instructions jbf, jbt, and jbr to jmpi. This is a V2 processors only situation. It's ignored on CK801 and CK802 targets (they don't support the jmpi instruction), and it's enabled by default for other processors.
  • -mbranch-stub / -mno-branch-stub โ€” pass through R_CKCORE_PCREL_IMM26BY2 relocations for bsr instructions to the linker.

This one is only available for bare-metal C-SKY V2 ELF targets, where it's enabled by default. It cannot be used in code that will be dynamically linked against shared libraries. ๐Ÿšจ

  • -force2bsr / -mforce2bsr / -no-force2bsr / -mno-force2bsr โ€” enable/disable transformation of jbsr instructions to bsr. This is always enabled (and -mno-force2bsr is ignored) for CK801/CK802 targets. It's also always enabled when -mbranch-stub is in effect.
  • -jsri2bsr / -mjsri2bsr / -no-jsri2bsr / -mno-jsri2bsr โ€” enable/disable transformation of jsri instructions to bsr. Enabled by default, slay.
  • -mnolrw / -mno-lrw โ€” enable/disable transformation of lrw instructions into a movih/ori pair.
  • -melrw / -mno-elrw โ€” enable/disable extended lrw instructions. Enabled by default for CK800-series processors.
  • -mlaf / -mliterals-after-func / -mno-laf / -mno-literals-after-func โ€” enable/disable placement of literal pools after each function.
  • -mlabr / -mliterals-after-br / -mno-labr / -mnoliterals-after-br โ€” enable/disable placement of literal pools after unconditional branches. Enabled by default.
  • -mistack / -mno-istack โ€” enable/disable interrupt stack instructions. Enabled by default on CK801, CK802, and CK802 processors. (That's literally what the page says โ€” CK802 twice, iconic of it ๐Ÿ’€)

The following options explicitly enable certain optional instructions. These features are also enabled implicitly by using -mcpu= to specify a processor that supports it. iykyk:

  • -mhard-float โ€” enable hard float instructions.
  • -mmp โ€” enable multiprocessor instructions.
  • -mcp โ€” enable coprocessor instructions.
  • -mcache โ€” enable cache prefetch instruction.
  • -msecurity โ€” enable C-SKY security instructions.
  • -mtrust โ€” enable C-SKY trust instructions.
  • -mdsp โ€” enable DSP instructions.
  • -medsp โ€” enable enhanced DSP instructions.
  • -mvdsp โ€” enable vector DSP instructions.

๐ŸŒˆ Epiphany moment

These ones are available when as is configured for an Epiphany processor:

  • -mepiphany โ€” specifies that both 32 and 16 bit instructions are allowed. This is the default behavior, main character energy.
  • -mepiphany16 โ€” restricts the permitted instructions to just the 16 bit set.

๐Ÿ“ H8/300, the Renesas era

@chapter H8/300 Dependent Features

Options

The Renesas H8/300 version of as has one machine-dependent option:

  • -h-tick-hex โ€” support H'00 style hex constants in addition to 0x00 style. Both aesthetics welcome ๐Ÿ’…
  • -mach=name โ€” sets the H8300 machine variant. The recognized machine names are: h8300h, h8300hn, h8300s, h8300sn, h8300sx and h8300sxn.

๐Ÿงš i386, x86 bestie

These options are available when as is configured for an i386 processor:

  • --32 / --x32 / --64 โ€” select the word size, either 32 bits or 64 bits. --32 implies Intel i386 architecture, while --x32 and --64 imply AMD x86-64 architecture with 32-bit or 64-bit word-size respectively.

These options are only available with the ELF object file format, and they require that the necessary BFD support has been included (on a 32-bit platform you have to add --enable-64-bit-bfd to configure enable 64-bit usage and use x86-64 as target platform). No shortcuts, bestie.

  • -n โ€” by default, x86 GAS replaces multiple nop instructions used for alignment within code sections with multi-byte nop instructions such as leal 0(%esi,1),%esi. This switch disables the optimization if a single byte nop (0x90) is explicitly specified as the fill byte for alignment.
  • --divide โ€” on SVR4-derived platforms, the character / is treated as a comment character, which means it can't be used in expressions. The --divide option turns / into a normal character. This does not disable / at the beginning of a line starting a comment, or affect using # for starting a comment.
  • -march=CPU[+EXTENSION...] โ€” specifies the target processor. The assembler will issue an error message if you attempt to assemble an instruction that won't execute on the target processor. The recognized processor names are: i8086, i186, i286, i386, i486, i586, i686, pentium, pentiumpro, pentiumii, pentiumiii, pentium4, prescott, nocona, core, core2, corei7, iamcu, k6, k6_2, athlon, opteron, k8, amdfam10, bdver1, bdver2, bdver3, bdver4, znver1, znver2, znver3, znver4, znver5, znver6, btver1, btver2, generic32 and generic64. That's the whole roster, no cap ๐Ÿ”ฅ

okay so, plot twist โ€” on top of the basic instruction set, the assembler can be told to accept a whole bunch of extension mnemonics. like, for example, -march=i686+sse4+vmx extends i686 with sse4 and vmx. ๐Ÿ’… and the extensions it supports rn are โ€” deep breath, bestie โ€” 8087, 287, 387, 687, cmov, fxsr, mmx, sse, sse2, sse3, sse4a, ssse3, sse4.1, sse4.2, sse4, avx, avx2, lahf_sahf, monitor, adx, rdseed, prfchw, smap, mpx, sha, rdpid, ptwrite, cet, gfni, vaes, vpclmulqdq, prefetchwt1, clflushopt, se1, clwb, movdiri, movdir64b, enqcmd, serialize, tsxldtrk, kl, widekl, hreset, avx512f, avx512cd, avx512er, avx512pf, avx512vl, avx512bw, avx512dq, avx512ifma, avx512vbmi, avx512_4fmaps, avx512_4vnniw, avx512_vpopcntdq, avx512_vbmi2, avx512_vnni, avx512_bitalg, avx512_vp2intersect, tdx, avx512_bf16, avx_vnni, avx512_fp16, avx512_bmm, prefetchi, avx_ifma, avx_vnni_int8, cmpccxadd, wrmsrns, msrlist, avx_ne_convert, rao_int, fred, lkgs, avx_vnni_int16, sha512, sm3, sm4, pbndkb, avx10.1, avx10.1/512, avx10.1/256, avx10.1/128, user_msr, msr_imm, apx_f, apx_nci, apx_ndd, apx_nf, apx_nci_ndd_nf, avx10.2, avx10.2/512, avx10.2/256, avx10.2/128, movrs, amx_int8, amx_bf16, amx_fp16, amx_complex, amx_transpose, amx_tf32, amx_fp8 amx_movrs, amx_avx512, amx_tile, vmx, vmfunc, smx, xsave, xsaveopt, xsavec, xsaves, aes, pclmul, fsgsbase, rdrnd, f16c, bmi2, fma, movbe, ept, lzcnt, popcnt, hle, rtm, tsx, invpcid, clflush, mwaitx, clzero, wbnoinvd, pconfig, waitpkg, uintr, cldemote, rdpru, mcommit, sev_es, lwp, fma4, xop, cx16, syscall, rdtscp, 3dnow, 3dnowa, sse4a, sse5, snp, invlpgb, tlbsync, rmpquery, rmpread, svme, gmism2, gmiccs, padlockrng2, padlockphe2, padlockxmodx and padlock. that's the whole squad, no cap. ๐ŸŒˆ

okay so important note: these extension mnemonics can be prefixed with no to revoke the respective (and any dependent) functionality. like, cancel culture but for CPU features. and ANOTHER note โ€” the suffixes permitted on -march=avx10.<N> enforce a vector length restriction. which is lowkey wild: despite these otherwise being "enabling" options, using these suffixes will disable all insns with wider vector or mask register operands. it's giving "yes but actually no". ๐Ÿ’€

and one more thing, bestie: when the .arch directive is used with -march, the .arch directive will take precedent. periodt.

  • -mtune=CPU โ€” this one specifies a processor to optimize for ๐ŸŽฏ. when it's used in conjunction with the -march option, only instructions of the processor specified by the -march option will be generated. valid CPU values are identical to the processor list of -march=CPU.
  • -moperand-check=none, -moperand-check=warning, -moperand-check=error โ€” these control whether the assembler checks certain instruction operands or operand combinations. example: an instruction where operand size cannot be inferred from its operands and also hasn't been specified by way of an instruction suffix. -moperand-check=none makes the assembler not perform these checks. -moperand-check=warning makes it issue a warning when respective checks fail โ€” and that's the default โœจ. -moperand-check=error makes it issue an error when respective checks fail.
  • -msse2avx โ€” tells the assembler to encode SSE instructions with VEX prefix, requiring AVX to be available ๐Ÿฆ‹. SSE instructions using extended GPRs will be encoded with EVEX prefix, requiring AVX512 or AVX10 to be available.
  • -muse-unaligned-vector-move โ€” tells the assembler to encode aligned vector move as unaligned vector move. sneaky but valid ๐Ÿ’….
  • -msse-check=none, -msse-check=warning, -msse-check=error โ€” control whether the assembler checks SSE instructions. -msse-check=none makes the assembler not check SSE instructions, which is the default. -msse-check=warning makes it issue a warning for any SSE instruction ๐Ÿซถ. -msse-check=error makes it issue an error for any SSE instruction.
  • -mavxscalar=128, -mavxscalar=256 โ€” control how the assembler should encode scalar AVX instructions. -mavxscalar=128 encodes scalar AVX instructions with 128bit vector length, which is the default. -mavxscalar=256 encodes scalar AVX instructions with 256bit vector length.
โš ๏ธ WARNING: Don't use this for production code - due to CPU errata the resulting code may not work on certain models. like, fr fr, do not ship this ๐Ÿ˜ญ
  • -mvexwig=0, -mvexwig=1 โ€” control how the assembler encodes VEX.W-ignored (WIG) VEX instructions. -mvexwig=0 encodes WIG VEX instructions with vex.w = 0, which is the default. -mvexwig=1 encodes WIG EVEX instructions with vex.w = 1.
โš ๏ธ WARNING: Don't use this for production code - due to CPU errata the resulting code may not work on certain models. same warning, same energy, still do not ship it ๐Ÿ’€
  • -mevexlig=128, -mevexlig=256, -mevexlig=512 โ€” control how the assembler encodes length-ignored (LIG) EVEX instructions. -mevexlig=128 encodes LIG EVEX instructions with 128bit vector length, which is the default. -mevexlig=256 and -mevexlig=512 encode LIG EVEX instructions with 256bit and 512bit vector length, respectively.
  • -mevexwig=0, -mevexwig=1 โ€” control how the assembler encodes w-ignored (WIG) EVEX instructions. -mevexwig=0 encodes WIG EVEX instructions with evex.w = 0, which is the default. -mevexwig=1 encodes WIG EVEX instructions with evex.w = 1.
  • -mmnemonic=att, -mmnemonic=intel โ€” specifies instruction mnemonic for matching instructions ๐ŸŽ€. heads up: the .att_mnemonic and .intel_mnemonic directives will take precedent.
  • -msyntax=att, -msyntax=intel โ€” specifies instruction syntax when processing instructions โœจ. again, the .att_syntax and .intel_syntax directives will take precedent.
  • -mnaked-reg โ€” specifies that registers don't require a % prefix. the .att_syntax and .intel_syntax directives will take precedent. naked registers, iconic honestly ๐Ÿซฃ
  • -madd-bnd-prefix โ€” forces the assembler to add BND prefix to all branches, even if such prefix was not explicitly specified in the source code. it's giving "I'm helping" ๐Ÿ˜Œ
  • -mno-shared โ€” on ELF target, the assembler normally optimizes out non-PLT relocations against defined non-weak global branch targets with default visibility. the -mshared option tells the assembler to generate code which may go into a shared library where all non-weak global branch targets with default visibility can be preempted. the resulting code is slightly bigger. this option only affects the handling of branch instructions.
  • -mbig-obj โ€” on PE/COFF target this option forces the use of big object file format, which allows more than 32768 sections. big object energy ๐Ÿ”ฅ
  • -momit-lock-prefix=no, -momit-lock-prefix=yes โ€” control how the assembler should encode lock prefix. this option is intended as a workaround for processors that fail on lock prefix.
๐Ÿšจ this option can only be safely used with single-core, single-thread computers. like, only. don't be out here on a 64-thread machine thinking it's fine.

-momit-lock-prefix=yes will omit all lock prefixes. -momit-lock-prefix=no will encode lock prefix as usual, which is the default.

  • -mfence-as-lock-add=no, -mfence-as-lock-add=yes โ€” control how the assembler should encode lfence, mfence and sfence. -mfence-as-lock-add=yes will encode lfence, mfence and sfence as lock addl $0x0, (%rsp) in 64-bit mode and lock addl $0x0, (%esp) in 32-bit mode. -mfence-as-lock-add=no will encode lfence, mfence and sfence as usual, which is the default. so extra, but valid ๐Ÿ’…
  • -mrelax-relocations=no, -mrelax-relocations=yes โ€” control whether the assembler should generate relax relocations, R_386_GOT32X, in 32-bit mode, or R_X86_64_GOTPCRELX and R_X86_64_REX_GOTPCRELX, in 64-bit mode. -mrelax-relocations=yes will generate relax relocations. -mrelax-relocations=no will not generate relax relocations.
  • -mtls-check=no, -mtls-check=yes โ€” control whether the assembler checks tls relocation ๐Ÿ‘€. -mtls-check=yes will check tls relocation. -mtls-check=no will not check tls relocation. the default can be controlled by a configure option --enable-x86-tls-check.
  • -malign-branch-boundary=NUM โ€” controls how the assembler should align branches with segment prefixes or NOP. NUM must be a power of 2. it should be 0 or no less than 16. branches will be aligned within NUM byte boundary. -malign-branch-boundary=0, which is the default, doesn't align branches.
  • -malign-branch=TYPE[+TYPE...] โ€” specifies types of branches to align. TYPE is a combination of jcc, which aligns conditional jumps, fused, which aligns fused conditional jumps, jmp, which aligns unconditional jumps, call which aligns calls, ret, which aligns rets, indirect, which aligns indirect jumps and calls. the default is -malign-branch=jcc+fused+jmp.
  • -malign-branch-prefix-size=NUM โ€” specifies the maximum number of prefixes on an instruction to align branches. NUM should be between 0 and 5. the default NUM is 5.
  • -mbranches-within-32B-boundaries โ€” aligns conditional jumps, fused conditional jumps and unconditional jumps within 32 byte boundary with up to 5 segment prefixes on an instruction. it is equivalent to -malign-branch-boundary=32 -malign-branch=jcc+fused+jmp -malign-branch-prefix-size=5. the default doesn't align branches. one flag, three flags' worth of chaos ๐Ÿ˜…
  • -mlfence-after-load=no, -mlfence-after-load=yes โ€” control whether the assembler should generate lfence after load instructions. -mlfence-after-load=yes will generate lfence. -mlfence-after-load=no will not generate lfence, which is the default. ๐ŸŽ€
  • -mlfence-before-indirect-branch=none, -mlfence-before-indirect-branch=all, -mlfence-before-indirect-branch=register, -mlfence-before-indirect-branch=memory โ€” ok so these control whether the assembler generates an lfence before indirect near branch instructions โœจ the deets:
    • -mlfence-before-indirect-branch=all โ€” generates lfence before indirect near branch via register, and issues a warning before indirect near branch via memory ๐Ÿซถ it also implicitly sets -mlfence-before-ret=shl when there's no explicit -mlfence-before-ret= hanging around.
    • -mlfence-before-indirect-branch=register โ€” generates lfence before indirect near branch via register ๐Ÿ’…
    • -mlfence-before-indirect-branch=memory โ€” issues a warning before indirect near branch via memory โญ
    • -mlfence-before-indirect-branch=none โ€” generates no lfence and issues no warning. this is the default ๐ŸŽ€
heads up bestie: lfence won't be generated before indirect near branch via register when you've got -mlfence-after-load=yes, because the lfence gets generated after loading the branch target register instead. iykyk ๐Ÿ’œ
  • -mlfence-before-ret=none, -mlfence-before-ret=shl, -mlfence-before-ret=or, -mlfence-before-ret=yes, -mlfence-before-ret=not โ€” same energy but for ret ๐ŸŒธ do we generate an lfence before it or not:
    • -mlfence-before-ret=or โ€” generates an or instruction with lfence ๐Ÿ”ฅ
    • -mlfence-before-ret=shl / -mlfence-before-ret=yes โ€” generates a shl instruction with lfence โœจ
    • -mlfence-before-ret=not โ€” generates a not instruction with lfence ๐Ÿ’ซ
    • -mlfence-before-ret=none โ€” generates no lfence. this one's the default ๐ŸŽ€
  • -mx86-used-note=no, -mx86-used-note=yes โ€” should the assembler generate GNU_PROPERTY_X86_ISA_1_USED and GNU_PROPERTY_X86_FEATURE_2_USED GNU property notes? that's the vibe check ๐Ÿ‘‘ and ngl the default here can be controlled by the --enable-x86-used-note configure option.
  • -mevexrcig=rne, -mevexrcig=rd, -mevexrcig=ru, -mevexrcig=rz โ€” how should the assembler encode SAE-only EVEX instructions, hmm? ๐Ÿฆ‹
    • -mevexrcig=rne โ€” encodes the RC bits of the EVEX instruction with 00. this is the default ๐Ÿ’–
    • -mevexrcig=rd โ€” encodes SAE-only EVEX instructions with 01 RC bits.
    • -mevexrcig=ru โ€” encodes SAE-only EVEX instructions with 10 RC bits.
    • -mevexrcig=rz โ€” encodes SAE-only EVEX instructions with 11 RC bits.
  • -mamd64, -mintel64 โ€” says the assembler should accept only AMD64 or Intel64 ISA in 64-bit mode ๐Ÿ™ˆ the default is to accept common, Intel64 only and AMD64 ISAs (so like, everything, chill).
  • -O0 | -O | -O1 | -O2 | -Os โ€” optimize instruction encoding for a smaller instruction size, periodt ๐Ÿ’…
    • -O and -O1 โ€” encode 64-bit register load instructions with 64-bit immediate as 32-bit register load instructions with 31-bit or 32-bits immediates; encode 64-bit register clearing instructions with 32-bit register clearing instructions; encode 256-bit/512-bit VEX/EVEX vector register clearing instructions with 128-bit VEX vector register clearing instructions; encode 128-bit/256-bit EVEX vector register load/store instructions with VEX vector register load/store instructions; and encode 128-bit/256-bit EVEX packed integer logical instructions with 128-bit/256-bit VEX packed integer logical. ate, no crumbs ๐Ÿ”ฅ
    • -O2 โ€” includes -O1 optimization plus encodes 256-bit/512-bit EVEX vector register clearing instructions with 128-bit EVEX vector register clearing instructions โœจ also, in 64-bit mode, VEX encoded instructions with commutative source operands will have their source operands swapped if that lets them use the 2-byte VEX prefix form instead of the 3-byte one ๐Ÿ‘€ and certain forms of AND as well as OR with the same (register) operand specified twice will also be changed to TEST.
    • -Os โ€” includes -O2 optimization plus encodes 16-bit, 32-bit and 64-bit register tests with immediate as 8-bit register test with immediate ๐ŸŽ€
    • -O0 โ€” turns off this optimization. back to basics bestie ๐Ÿ˜Œ

๐ŸŒˆ The following options are available when as is configured for the Ubicom IP2K series.

  • -mip2022ext โ€” specifies that the extended IP2022 instructions are allowed ๐Ÿ’ซ
  • -mip2022 โ€” restores the default behaviour, which restricts the permitted instructions to just the basic IP2022 ones ๐Ÿซถ

๐Ÿ“ The following options are available when as is configured for the Renesas M32C and M16C processors.

  • -m32c โ€” assemble M32C instructions.
  • -m16c โ€” assemble M16C instructions (the default) ๐Ÿ’–
  • -relax โ€” enable support for link-time relaxations โœจ
  • -h-tick-hex โ€” support H'00 style hex constants in addition to 0x00 style ๐Ÿ‘‘

๐Ÿฆ‹ The following options are available when as is configured for the Renesas M32R (formerly Mitsubishi M32R) series.

  • --m32rx โ€” specify which processor in the M32R family is the target ๐ŸŒธ the default is normally the M32R, but this option changes it to the M32RX.
  • --warn-explicit-parallel-conflicts or --Wp โ€” produce warning messages when questionable parallel constructs are encountered ๐Ÿ˜ญ
  • --no-warn-explicit-parallel-conflicts or --Wnp โ€” do not produce warning messages when questionable parallel constructs are encountered ๐Ÿ™ˆ

๐Ÿ’œ The following options are available when as is configured for the Motorola 68000 series.

  • -l โ€” shorten references to undefined symbols, to one word instead of two.
  • -m68000 | -m68008 | -m68010 | -m68020 | -m68030 | -m68040 | -m68060 | -m68302 | -m68331 | -m68332 | -m68333 | -m68340 | -mcpu32 | -m5200 โ€” specify what processor in the 68000 family is the target ๐Ÿ”ฅ the default is normally the 68020, but this can be changed at configuration time.
  • -m68881 | -m68882 | -mno-68881 | -mno-68882 โ€” the target machine does (or does not) have a floating-point coprocessor ๐Ÿ’… the default is to assume a coprocessor for 68020, 68030, and cpu32. and like, even though the basic 68000 is not compatible with the 68881, a combination of the two can be specified, since it's possible to do emulation of the coprocessor instructions with the main processor ๐Ÿคฏ iconic.
  • -m68851 | -mno-68851 โ€” the target machine does (or does not) have a memory-management unit coprocessor ๐Ÿซถ the default is to assume an MMU for 68020 and up.

For details about the PDP-11 machine dependent features options, see PDP-11-Options ๐Ÿ“–

  • -mpic | -mno-pic โ€” generate position-independent (or position-dependent) code โœจ the default is -mpic.
  • -mall, -mall-extensions โ€” enable all instruction set extensions ๐Ÿ”ฅ this is the default.
  • -mno-extensions โ€” disable all instruction set extensions ๐Ÿ’€
  • -mextension | -mno-extension โ€” enable (or disable) a particular instruction set extension ๐ŸŽ€
  • -mcpu โ€” enable the instruction set extensions supported by a particular CPU, and disable all other extensions ๐Ÿ‘‘
  • -mmachine โ€” enable the instruction set extensions supported by a particular machine model, and disable all other extensions ๐ŸŒŸ

๐ŸŒธ The following options are available when as is configured for a picoJava processor.

  • -mb โ€” generate "big endian" format output.
  • -ml โ€” generate "little endian" format output ๐ŸŒˆ

๐Ÿงš The following options are available when as is configured for a PRU processor.

  • -mlink-relax โ€” assume that LD would optimize LDI32 instructions by checking the upper 16 bits of the expression ๐Ÿซถ if they're all zeros, then LD would shorten the LDI32 instruction to a single LDI. in such case as will output DIFF relocations for diff expressions โœจ
  • -mno-link-relax โ€” assume that LD would not optimize LDI32 instructions ๐Ÿ˜Œ as a consequence, DIFF relocations will not be emitted.
  • -mno-warn-regname-label โ€” do not warn if a label name matches a register name ๐Ÿ™ˆ usually assembler programmers will want this warning to be emitted. C compilers may want to turn this off.
  • -mcore-revision=revision โ€” specifies the PRU core revision to assemble for ๐Ÿ’… the following revisions are recognized: "V1", "V2", "V3" and "V4". the assembler defaults to "V3" ๐ŸŽ€

๐Ÿ‘‘ The following options are available when as is configured for a MIPS processor.

  • -G num โ€” sets the largest size of an object that can be referenced implicitly with the gp register ๐ŸŒŸ it's only accepted for targets that use ECOFF format, such as a DECstation running Ultrix. the default value is 8.
  • -EB โ€” generate "big endian" format output.
  • -EL โ€” generate "little endian" format output ๐ŸŒˆ
  • -mips1, -mips2, -mips3, -mips4, -mips5, -mips32, -mips32r2, -mips32r3, -mips32r5, -mips32r6, -mips64, -mips64r2, -mips64r3, -mips64r5, -mips64r6 โ€” generate code for a particular MIPS Instruction Set Architecture level ๐Ÿ”ฅ and the aliases are giving:
    • -mips1 is an alias for -march=r3000
    • -mips2 is an alias for -march=r6000
    • -mips3 is an alias for -march=r4000
    • -mips4 is an alias for -march=r8000
    • -mips5, -mips32, -mips32r2, -mips32r3, -mips32r5, -mips32r6, -mips64, -mips64r2, -mips64r3, -mips64r5, and -mips64r6 correspond to generic MIPS V, MIPS32, MIPS32 Release 2, MIPS32 Release 3, MIPS32 Release 5, MIPS32 Release 6, MIPS64, MIPS64 Release 2, MIPS64 Release 3, MIPS64 Release 5, and MIPS64 Release 6 ISA processors, respectively ๐Ÿ’…
  • -march=cpu โ€” generate code for a particular MIPS CPU โœจ
  • -mtune=cpu โ€” schedule and tune for a particular MIPS CPU ๐ŸŽ€
  • -mfix7000 | -mno-fix7000 โ€” cause nops to be inserted if the read of the destination register of an mfhi or mflo instruction occurs in the following two instructions ๐Ÿ‘€
  • -mfix-rm7000 | -mno-fix-rm7000 โ€” cause nops to be inserted if a dmult or dmultu instruction is followed by a load instruction ๐Ÿซถ
  • -mfix-r5900 | -mno-fix-r5900 โ€” do not attempt to schedule the preceding instruction into the delay slot of a branch instruction placed at the end of a short loop of six instructions or fewer, and always schedule a nop instruction there instead ๐Ÿ’€ the short loop bug under certain conditions causes loops to execute only once or twice, due to a hardware bug in the R5900 chip ๐Ÿ˜ญ not the vibe.
  • -mdebug | -no-mdebug โ€” cause stabs-style debugging output to go into an ECOFF-style .mdebug section instead of the standard ELF .stabs sections โœจ
  • -mpdr | -mno-pdr โ€” control generation of .pdr sections ๐ŸŽ€
  • -mgp32 | -mfp32 โ€” the register sizes are normally inferred from the ISA and ABI, but these flags force a certain group of registers to be treated as 32 bits wide at all times ๐ŸŒธ -mgp32 controls the size of general-purpose registers and -mfp32 controls the size of floating-point registers ๐Ÿ’–
  • -mgp64, -mfp64 โ€” so normally your register sizes are just inferred from the ISA and ABI, right? But these flags force a certain group of registers to be treated as 64 bits wide at all times. -mgp64 controls the size of general-purpose registers, and -mfp64 controls the size of floating-point registers. ๐Ÿ’…
  • -mfpxx โ€” register sizes are normally inferred from the ISA and ABI, but using this flag in combination with -mabi=32 enables an ABI variant that will operate correctly with floating-point registers that are 32 or 64 bits wide. flexible queen behavior โœจ
  • -modd-spreg, -mno-odd-spreg โ€” enable use of floating-point operations on odd-numbered single-precision registers when supported by the ISA. -mfpxx implies -mno-odd-spreg, otherwise the default is -modd-spreg. odd numbers stay booked and busy ๐ŸŽ€
  • -mips16, -no-mips16 โ€” generate code for the MIPS 16 processor. This is equivalent to putting .module mips16 at the start of the assembly file. -no-mips16 turns off this option.
  • -mmips16e2, -mno-mips16e2 โ€” enable the use of MIPS16e2 instructions in MIPS16 mode. This is equivalent to putting .module mips16e2 at the start of the assembly file. -mno-mips16e2 turns off this option.
  • -mmicromips, -mno-micromips โ€” generate code for the microMIPS processor. This is equivalent to putting .module micromips at the start of the assembly file. -mno-micromips turns off this option. This is equivalent to putting .module nomicromips at the start of the assembly file.
  • -msmartmips, -mno-smartmips โ€” enables the SmartMIPS extension to the MIPS32 instruction set. This is equivalent to putting .module smartmips at the start of the assembly file. -mno-smartmips turns off this option.
  • -mips3d, -no-mips3d โ€” generate code for the MIPS-3D Application Specific Extension. This tells the assembler to accept MIPS-3D instructions. -no-mips3d turns off this option.
  • -mdmx, -no-mdmx โ€” generate code for the MDMX Application Specific Extension. This tells the assembler to accept MDMX instructions. -no-mdmx turns off this option.
  • -mdsp, -mno-dsp โ€” generate code for the DSP Release 1 Application Specific Extension. This tells the assembler to accept DSP Release 1 instructions. -mno-dsp turns off this option.
  • -mdspr2, -mno-dspr2 โ€” generate code for the DSP Release 2 Application Specific Extension. This option implies -mdsp. This tells the assembler to accept DSP Release 2 instructions. -mno-dspr2 turns off this option.
  • -mdspr3, -mno-dspr3 โ€” generate code for the DSP Release 3 Application Specific Extension. This option implies -mdsp and -mdspr2. This tells the assembler to accept DSP Release 3 instructions. -mno-dspr3 turns off this option.
  • -mmsa, -mno-msa โ€” generate code for the MIPS SIMD Architecture Extension. This tells the assembler to accept MSA instructions. -mno-msa turns off this option.
  • -mxpa, -mno-xpa โ€” generate code for the MIPS eXtended Physical Address (XPA) Extension. This tells the assembler to accept XPA instructions. -mno-xpa turns off this option.
  • -mmt, -mno-mt โ€” generate code for the MT Application Specific Extension. This tells the assembler to accept MT instructions. -mno-mt turns off this option.
  • -mmcu, -mno-mcu โ€” generate code for the MCU Application Specific Extension. This tells the assembler to accept MCU instructions. -mno-mcu turns off this option.
  • -mcrc, -mno-crc โ€” generate code for the MIPS cyclic redundancy check (CRC) Application Specific Extension. This tells the assembler to accept CRC instructions. -mno-crc turns off this option.
  • -mginv, -mno-ginv โ€” generate code for the Global INValidate (GINV) Application Specific Extension. This tells the assembler to accept GINV instructions. -mno-ginv turns off this option.
  • -mloongson-mmi, -mno-loongson-mmi โ€” generate code for the Loongson MultiMedia extensions Instructions (MMI) Application Specific Extension. This tells the assembler to accept MMI instructions. -mno-loongson-mmi turns off this option.
  • -mloongson-cam, -mno-loongson-cam โ€” generate code for the Loongson Content Address Memory (CAM) instructions. This tells the assembler to accept Loongson CAM instructions. -mno-loongson-cam turns off this option.
  • -mloongson-ext, -mno-loongson-ext โ€” generate code for the Loongson EXTensions (EXT) instructions. This tells the assembler to accept Loongson EXT instructions. -mno-loongson-ext turns off this option.
  • -mloongson-ext2, -mno-loongson-ext2 โ€” generate code for the Loongson EXTensions R2 (EXT2) instructions. This option implies -mloongson-ext. This tells the assembler to accept Loongson EXT2 instructions. -mno-loongson-ext2 turns off this option.
  • -minsn32, -mno-insn32 โ€” only use 32-bit instruction encodings when generating code for the microMIPS processor. This option inhibits the use of any 16-bit instructions. This is equivalent to putting .set insn32 at the start of the assembly file. -mno-insn32 turns off this option. This is equivalent to putting .set noinsn32 at the start of the assembly file. By default -mno-insn32 is selected, allowing all instructions to be used. no tiny encodings allowed, we're going full size ๐Ÿ’€
  • --construct-floats, --no-construct-floats โ€” the --no-construct-floats option disables the construction of double width floating point constants by loading the two halves of the value into the two single width floating point registers that make up the double width register. By default --construct-floats is selected, allowing construction of these floating point constants.
  • --relax-branch, --no-relax-branch โ€” the --relax-branch option enables the relaxation of out-of-range branches. By default --no-relax-branch is selected, causing any out-of-range branches to produce an error. bestie the default is strict, okurrr ๐Ÿ˜ญ
  • -mignore-branch-isa, -mno-ignore-branch-isa โ€” ignore branch checks for invalid transitions between ISA modes. The semantics of branches does not provide for an ISA mode switch, so in most cases the ISA mode a branch has been encoded for has to be the same as the ISA mode of the branch's target label. Therefore GAS has checks implemented that verify in branch assembly that the two ISA modes match. -mignore-branch-isa disables these checks. By default -mno-ignore-branch-isa is selected, causing any invalid branch requiring a transition between ISA modes to produce an error. the vibe check is ON by default ๐Ÿ”ฅ
  • -mnan=encoding โ€” select between the IEEE 754-2008 (-mnan=2008) or the legacy (-mnan=legacy) NaN encoding format. The latter is the default.
  • --emulation=name โ€” ok so history lesson ๐Ÿซถ this option was formerly used to switch between ELF and ECOFF output on targets like IRIX 5 that supported both. MIPS ECOFF support was removed in GAS 2.24, so the option now serves little purpose. It is retained for backwards compatibility.

The available configuration names are: mipself, mipslelf and mipsbelf. Choosing mipself now has no effect, since the output is always ELF. mipslelf and mipsbelf select little- and big-endian output respectively, but -EL and -EB are now the preferred options instead.

  • -nocpp โ€” as ignores this option. It is accepted for compatibility with the native tools. literally just vibing in the parser, doing nothing ๐Ÿฆ‹
  • --trap, --no-trap, --break, --no-break โ€” control how to deal with multiplication overflow and division by zero. --trap or --no-break (which are synonyms) take a trap exception (and only work for Instruction Set Architecture level 2 and higher); --break or --no-trap (also synonyms, and the default) take a break exception.
  • -n โ€” when this option is used, as will issue a warning every time it generates a nop instruction from a macro. not me getting called out every single time I emit a nop ๐Ÿ™ˆ

๐ŸŒธ when as is configured for a LoongArch processor ๐ŸŒธ

The following options are available when as is configured for a LoongArch processor.

  • -fpic, -fPIC โ€” generate position-independent code
  • -fno-pic โ€” don't generate position-independent code (default)

๐Ÿงš when as is configured for a Meta processor ๐Ÿงš

The following options are available when as is configured for a Meta processor.

  • "-mcpu=metac11" โ€” generate code for Meta 1.1.
  • "-mcpu=metac12" โ€” generate code for Meta 1.2.
  • "-mcpu=metac21" โ€” generate code for Meta 2.1.
  • "-mfpu=metac21" โ€” allow code to use FPU hardware of Meta 2.1.

See the info pages for documentation of the MMIX-specific options. (yes, that's the whole MMIX situation, go read the info pages bestie ๐Ÿ’œ)


๐Ÿ‘‘ when as is configured for a NDS32 processor ๐Ÿ‘‘

The following options are available when as is configured for a NDS32 processor.

  • "-O1" โ€” optimize for performance.
  • "-Os" โ€” optimize for space.
  • "-EL" โ€” produce little endian data output.
  • "-EB" โ€” produce little endian data output.
not me side-eying -EB saying "little endian" too ๐Ÿ‘€ that is exactly what the page says, so I'm passing it along verbatim, no edits, no notes. take it up with the docs, bestie.
  • "-mpic" โ€” generate PIC.
  • "-mno-fp-as-gp-relax" โ€” suppress fp-as-gp relaxation for this file.
  • "-mb2bb-relax" โ€” back-to-back branch optimization.
  • "-mno-all-relax" โ€” suppress all relaxation for this file.
  • "-march=<arch name>" โ€” assemble for architecture <arch name> which could be v3, v3j, v3m, v3f, v3s, v2, v2j, v2f, v2s.
  • "-mbaseline=<baseline>" โ€” assemble for baseline <baseline> which could be v2, v3, v3m.
  • "-mfpu-freg=FREG" โ€” specify a FPU configuration.
"0      8 SP /  4 DP registers"
"1     16 SP /  8 DP registers"
"2     32 SP / 16 DP registers"
"3     32 SP / 32 DP registers"
  • "-mabi=abi" โ€” specify a abi version <abi> could be v1, v2, v2fp, v2fpp.
  • "-m[no-]mac" โ€” enable/disable Multiply instructions support.
  • "-m[no-]div" โ€” enable/disable Divide instructions support.
  • "-m[no-]16bit-ext" โ€” enable/disable 16-bit extension
  • "-m[no-]dx-regs" โ€” enable/disable d0/d1 registers
  • "-m[no-]perf-ext" โ€” enable/disable Performance extension
  • "-m[no-]perf2-ext" โ€” enable/disable Performance extension 2
  • "-m[no-]string-ext" โ€” enable/disable String extension
  • "-m[no-]reduced-regs" โ€” enable/disable Reduced Register configuration (GPR16) option
  • "-m[no-]audio-isa-ext" โ€” enable/disable AUDIO ISA extension
  • "-m[no-]fpu-sp-ext" โ€” enable/disable FPU SP extension
  • "-m[no-]fpu-dp-ext" โ€” enable/disable FPU DP extension
  • "-m[no-]fpu-fma" โ€” enable/disable FPU fused-multiply-add instructions
  • "-mall-ext" โ€” turn on all extensions and instructions support. the "give me everything on the menu" option, iconic ๐ŸŒˆ

โญ when as is configured for a PowerPC processor โญ

The following options are available when as is configured for a PowerPC processor.

  • -a32 โ€” generate ELF32 or XCOFF32.
  • -a64 โ€” generate ELF64 or XCOFF64.
  • -K PIC โ€” sets EF_PPC_RELOCATABLE_LIB in the ELF flags. yes bestie it's literally one job and it does it ๐Ÿ’…
  • -mpwrx, -mpwr2 โ€” generate code for POWER/2 (RIOS2). ๐Ÿฆ‹
  • -mpwr โ€” generate code for POWER (RIOS1).
  • -m601 โ€” generate code for PowerPC 601.
  • -mppc, -mppc32, -m603, -m604 โ€” generate code for PowerPC 603/604.
  • -m403, -m405 โ€” generate code for PowerPC 403/405.
  • -m440 โ€” generate code for PowerPC 440. BookE and some 405 instructions, iykyk.
  • -m464 โ€” generate code for PowerPC 464.
  • -m476 โ€” generate code for PowerPC 476.
  • -m7400, -m7410, -m7450, -m7455 โ€” generate code for PowerPC 7400/7410/7450/7455.
  • -m750cl, -mgekko, -mbroadway โ€” generate code for PowerPC 750CL/Gekko/Broadway.
  • -m821, -m850, -m860 โ€” generate code for PowerPC 821/850/860.
  • -mppc64, -m620 โ€” generate code for PowerPC 620/625/630.
  • -me200z2, -me200z4 โ€” generate code for e200 variants: e200z2 with LSP, e200z4 with SPE.
  • -me300 โ€” generate code for the PowerPC e300 family. ๐Ÿ‘‘
  • -me500, -me500x2 โ€” generate code for the Motorola e500 core complex.
  • -me500mc โ€” generate code for the Freescale e500mc core complex.
  • -me500mc64 โ€” generate code for the Freescale e500mc64 core complex.
  • -me5500 โ€” generate code for the Freescale e5500 core complex.
  • -me6500 โ€” generate code for the Freescale e6500 core complex.
  • -mlsp โ€” enable LSP instructions. (Disables SPE and SPE2 โ€” it's giving "choose your fighter" ๐Ÿ˜ญ)
  • -mspe โ€” generate code for Motorola SPE instructions. (Disables LSP.)
  • -mspe2 โ€” generate code for Freescale SPE2 instructions. (Disables LSP.)
  • -mtitan โ€” generate code for the AppliedMicro Titan core complex.
  • -mppc64bridge โ€” generate code for PowerPC 64, including bridge insns.
  • -mbooke โ€” generate code for 32-bit BookE.
  • -ma2 โ€” generate code for the A2 architecture.
  • -maltivec โ€” generate code for processors with AltiVec instructions. โœจ
  • -mvle โ€” generate code for Freescale PowerPC VLE instructions.
  • -mvsx โ€” generate code for processors with Vector-Scalar (VSX) instructions.
  • -mhtm โ€” generate code for processors with Hardware Transactional Memory instructions.
  • -mpower4, -mpwr4 โ€” generate code for the Power4 architecture.
  • -mpower5, -mpwr5, -mpwr5x โ€” generate code for the Power5 architecture.
  • -mpower6, -mpwr6 โ€” generate code for the Power6 architecture.
  • -mpower7, -mpwr7 โ€” generate code for the Power7 architecture.
  • -mpower8, -mpwr8 โ€” generate code for the Power8 architecture.
  • -mpower9, -mpwr9 โ€” generate code for the Power9 architecture.
  • -mpower10, -mpwr10 โ€” generate code for the Power10 architecture.
  • -mpower11, -mpwr11 โ€” generate code for the Power11 architecture.
  • -mfuture โ€” generate code for the 'future' architecture. she's ahead of her time, literally ๐Ÿซถ
  • -mcell, -mcell โ€” generate code for the Cell Broadband Engine architecture. (yes, the original lists it twice โ€” iconic of it, honestly ๐ŸŽ€)
  • -mcom โ€” generate code for Power/PowerPC common instructions.
  • -many โ€” generate code for any architecture (PWR/PWRX/PPC). no thoughts, just range ๐ŸŒˆ
  • -mregnames โ€” allow symbolic names for registers.
  • -mno-regnames โ€” do not allow symbolic names for registers.
  • -mrelocatable โ€” support for GCC's -mrelocatable option.
  • -mrelocatable-lib โ€” support for GCC's -mrelocatable-lib option.
  • -memb โ€” set the PPC_EMB bit in ELF flags.
  • -mlittle, -mlittle-endian, -le โ€” generate code for a little endian machine.
  • -mbig, -mbig-endian, -be โ€” generate code for a big endian machine. big endian stans rise ๐Ÿ™ˆ
  • -nops=count โ€” if an alignment directive inserts more than count nops, put a branch at the beginning to skip execution of the nops. efficiency queen ๐Ÿ’…

So! The next batch of options is available when as is configured for a RISC-V processor. slay, let's go ๐Ÿงš

  • -fpic, -fPIC โ€” generate position-independent code.
  • -fno-pic โ€” don't generate position-independent code (this one's the default).
  • -march=ISA|Profiles|Profiles_ISA โ€” select the base isa, as specified by ISA or Profiles or Profies_ISA. (yes, that's spelled Profies_ISA in the source, we don't edit, we respect ๐Ÿซก) For example -march=rv32ima -march=RVI20U64 -march=RVI20U64_d. If this option and the architecture attributes aren't set, then the assembler will check the default configure setting --with-arch=ISA.
  • -misa-spec=ISAspec โ€” select the default isa spec version. If the version of ISA isn't set by -march, then the assembler helps to set the version according to the default chosen spec. If this option isn't set, then the assembler will check the default configure setting --with-isa-spec=ISAspec.
  • -mpriv-spec=PRIVspec โ€” select the privileged spec version. We can decide whether the CSR is valid or not according to the chosen spec. If this option and the privilege attributes aren't set, then the assembler will check the default configure setting --with-priv-spec=PRIVspec.
  • -mabi=ABI โ€” selects the ABI, which is either "ilp32" or "lp64", optionally followed by "f", "d", or "q" to indicate single-precision, double-precision, or quad-precision floating-point calling convention, or none or "e" to indicate the soft-float calling convention ("e" indicates a soft-float RVE ABI). so many letters, all of them valid, we love a flexible queen ๐Ÿ’–
  • -mrelax โ€” take advantage of linker relaxations to reduce the number of instructions required to materialize symbol addresses. (default โ€” yes bestie, it's already on)
  • -mno-relax โ€” don't do linker relaxations.
  • -march-attr โ€” generate the default contents for the riscv elf attribute section if the .attribute directives are not set. This section is used to record the information that a linker or runtime loader needs to check compatibility. This information includes ISA string, stack alignment requirement, unaligned memory accesses, and the major, minor and revision version of privileged specification.
  • -mno-arch-attr โ€” don't generate the default riscv elf attribute section if the .attribute directives are not set.
  • -mcsr-check โ€” enable the CSR checking for the ISA-dependent CRS and the read-only CSR. The ISA-dependent CSR are only valid when the specific ISA is set. The read-only CSR can not be written by the CSR instructions. (no cap, read-only means read-only ๐Ÿ”ฅ)
  • -mno-csr-check โ€” don't do CSR checking.
  • -mlittle-endian โ€” generate code for a little endian machine.
  • -mbig-endian โ€” generate code for a big endian machine.
Head's up bestie: for documentation of the RX-specific options, see the info pages. ๐Ÿ“–

Next up, the options available when as is configured for the s390 processor family. z/Architecture girlies wya ๐ŸŽ€

  • -m31, -m64 โ€” select the word size, either 31/32 bits or 64 bits.
  • -mesa, -mzarch โ€” select the architecture mode, either the Enterprise System Architecture (esa) or the z/Architecture mode (zarch).
  • -march=processor โ€” specify which s390 processor variant is the target: g5 (or arch3), g6, z900 (or arch5), z990 (or arch6), z9-109, z9-ec (or arch7), z10 (or arch8), z196 (or arch9), zEC12 (or arch10), z13 (or arch11), z14 (or arch12), z15 (or arch13), z16 (or arch14), or z17 (or arch15). that's a whole rollout, she's got lore ๐Ÿ˜ญ
  • -mregnames, -mno-regnames โ€” allow or disallow symbolic names for registers.
  • -mwarn-areg-zero โ€” warn whenever the operand for a base or index register has been specified but evaluates to zero.
  • -mwarn-regtype-mismatch=strict, -mwarn-regtype-mismatch=relaxed, -mwarn-regtype-mismatch=no, -mno-warn-regtype-mismatch โ€” controls whether the assembler performs register name type checks and generates a warning message in case of a mismatch with the operand register type.

The default (which can be restored by using the relaxed argument) is to perform relaxed register name type checks, which allow floating point register (FPR) names %f0 to %f15 to be specified as argument to vector register (VR) operands and vector register (VR) names %v0 to %v15 to be specified as argument to floating point register (FPR) operands. This is acceptable as the FPR are embedded into the lower half of the VR.

Using the strict argument, strict register name type checks are performed. The no argument, which is equivalent to -mno-warn-regtype-mismatch, disables any register name type checks. choose your vibe wisely bestie ๐Ÿ’…


And now, the options available when as is configured for a TMS320C6000 processor. DSP besties we see you ๐Ÿฆ‹

  • -march=arch โ€” enable (only) instructions from architecture arch. By default, all instructions are permitted.

The following values of arch are accepted: "c62x", "c64x", "c64x+", "c67x", "c67x+", "c674x".

  • -mdsbt, -mno-dsbt โ€” the -mdsbt option causes the assembler to generate the "Tag_ABI_DSBT" attribute with a value of 1, indicating that the code is using DSBT addressing. The -mno-dsbt option, the default, causes the tag to have a value of 0, indicating that the code does not use DSBT addressing. The linker will emit a warning if objects of different type (DSBT and non-DSBT) are linked together. โš ๏ธ
  • -mpid=no, -mpid=near, -mpid=far โ€” the -mpid= option causes the assembler to generate the "Tag_ABI_PID" attribute with a value indicating the form of data addressing used by the code.
    • -mpid=no, the default, indicates position-dependent data addressing.
    • -mpid=near indicates position-independent addressing with GOT accesses using near DP addressing.
    • -mpid=far indicates position-independent addressing with GOT accesses using far DP addressing.

The linker will emit a warning if objects built with different settings of this option are linked together. yeah, mixing them is a whole situation ๐Ÿ’€

  • -mpic, -mno-pic โ€” the -mpic option causes the assembler to generate the "Tag_ABI_PIC" attribute with a value of 1, indicating that the code is using position-independent code addressing. The "-mno-pic" option, the default, causes the tag to have a value of 0, indicating position-dependent code addressing. The linker will emit a warning if objects of different type (position-dependent and position-independent) are linked together.
  • -mbig-endian, -mlittle-endian โ€” generate code for the specified endianness. The default is little-endian.

Then, options available when as is configured for a TILE-Gx processor. short list, main character energy โœจ

  • -m32 | -m64 โ€” select the word size, either 32 bits or 64 bits.
  • -EB | -EL โ€” select the endianness, either big-endian (-EB) or little-endian (-EL).

The following option is available when as is configured for a Visium processor. just one flag, she's lowkey mysterious ๐ŸŽ€

  • -mtune=arch โ€” this option specifies the target architecture. If an attempt is made to assemble an instruction that will not execute on the target architecture, the assembler will issue an error message. ๐Ÿšจ

The following names are recognized: "mcm24" "mcm" "gr5" "gr6"


The following options are available when as is configured for an Xtensa processor. ๐Ÿ‘€ (coming right upโ€ฆ)

  • --text-section-literals, --no-text-section-literals โ€” okay so this is the literal-pool vibe check ๐Ÿ’…. The default is --no-text-section-literals, which puts literals in separate sections in the output file so the literal pool can be placed in a data RAM/ROM. With --text-section-literals, the literals are interspersed in the text section to keep them as close as possible to their references. This may be necessary for large assembly files, where the literals would otherwise be out of range of the L32R instructions in the text section. Literals are grouped into pools following .literal_position directives or preceding ENTRY instructions. These options only affect literals referenced via PC-relative L32R instructions; literals for absolute mode L32R instructions are handled separately.
  • --auto-litpools, --no-auto-litpools โ€” another literal-pool control, bestie โœจ. The default is --no-auto-litpools, which in the absence of --text-section-literals places literals in separate sections in the output file, letting the literal pool go in a data RAM/ROM. With --auto-litpools, the literals are interspersed in the text section to keep them as close as possible to their references, and explicit .literal_position directives are not required. This may be necessary for very large functions, where a single literal pool at the beginning of the function may not be reachable by L32R instructions at the end. These options only affect literals referenced via PC-relative L32R instructions; literals for absolute mode L32R instructions are handled separately. When used together with --text-section-literals, --auto-litpools takes precedence ๐Ÿ‘‘.
  • --absolute-literals, --no-absolute-literals โ€” tells the assembler whether L32R instructions use absolute or PC-relative addressing. If the processor includes the absolute addressing option, the default is to use absolute L32R relocations. Otherwise, only the PC-relative L32R relocations can be used.
  • --target-align, --no-target-align โ€” turns automatic alignment on or off to reduce branch penalties at some expense in code size. This optimization is enabled by default. Note that the assembler will always align instructions like LOOP that have fixed alignment requirements.
  • --longcalls, --no-longcalls โ€” turns transformation of call instructions on or off so calls can reach across a greater range of addresses. This option should be used when call targets can potentially be out of range. It may degrade both code size and performance, but the linker can generally optimize away the unnecessary overhead when a call ends up within range. The default is --no-longcalls.
  • --transform, --no-transform โ€” turns all assembler transformations of Xtensa instructions on or off, including both relaxation and optimization. The default is --transform; --no-transform should only be used in the rare cases when the instructions must be exactly as specified in the assembly source. Using --no-transform causes out of range instruction operands to be errors ๐Ÿ˜ญ.
  • --rename-section oldname=newname โ€” renames the oldname section to newname. This option can be used multiple times to rename multiple sections.
  • --trampolines, --no-trampolines โ€” turns transformation of jump instructions on or off so jumps can reach across a greater range of addresses. This option should be used when jump targets can potentially be out of range. In the absence of such jumps this option does not affect code size or performance. The default is --trampolines.
  • --abi-windowed, --abi-call0 โ€” chooses the ABI tag written to the .xtensa.info section. The ABI tag indicates the ABI of the assembly code. A warning is issued by the linker on an attempt to link object files with inconsistent ABI tags. Default ABI is chosen by the Xtensa core configuration.

๐ŸŽฎ Z80 Dependent Features

The following options are available when as is configured for an Z80 processor.

@chapter Z80 Dependent Features

๐ŸŽ›๏ธ Command-line Options

  • -march=CPU[-EXT...][+EXT...] โ€” this specifies the target processor. The assembler will issue an error message if an attempt is made to assemble an instruction which will not execute on the target processor. The following processor names are recognized: z80, z180, ez80, gbz80, z80n, r800. In addition to the basic instruction set, the assembler can be told to accept some extension mnemonics. For example, -march=z180+sli+infc extends z180 with SLI instructions and IN F,(C). The following extensions are currently supported:
    • full โ€” all known instructions
    • adl โ€” ADL CPU mode by default, eZ80 only
    • sli โ€” instruction known as SLI, SLL or SL1
    • xyhl โ€” instructions with halves of index registers: IXL, IXH, IYL, IYH
    • xdcb โ€” instructions like RotOp (II+d),R and BitOp n,(II+d),R
    • infc โ€” instruction IN F,(C) or IN (C)
    • outc0 โ€” instruction OUT (C),0

Note that rather than extending a basic instruction set, the extension mnemonics starting with - revoke the respective functionality: -march=z80-full+xyhl first removes all default extensions and adds support for index registers halves only.

If this option is not specified then -march=z80+xyhl+infc is assumed.

  • -local-prefix=prefix โ€” marks all labels with the specified prefix as local. But such a label can be marked global explicitly in the code. This option does not change the default local label prefix .L; it just adds a new one.
  • -colonless โ€” accepts colonless labels. All symbols at line begin are treated as labels.
  • -sdcc โ€” accepts assembler code produced by SDCC.
  • -fp-s=FORMAT โ€” single precision floating point numbers format. Default: ieee754 (32 bit).
  • -fp-d=FORMAT โ€” double precision floating point numbers format. Default: ieee754 (64 bit).

๐ŸŒˆ SEE ALSO

gcc(1), ld(1), and the Info entries for binutils and ld.

Copyright (c) 1991-2026 Free Software Foundation, Inc.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license is included in the section entitled โ€œGNU Free Documentation Licenseโ€.


okay bye bestie โ€” page AS(1) from binutils-2.47, dated 2026-07-30 ๐Ÿ’–โœจ

๐Ÿ“ฆ where this page comes from