ARM Options (Using the GNU Compiler Collection (GCC))

#### 3.20.5 ARM Options ¶

These ‘`-m`’ options are defined for the ARM port:

`-mabi=name` ¶

  Generate code for the specified ABI. Permissible values are: ‘`apcs-gnu`’, ‘`atpcs`’, ‘`aapcs`’ and ‘`aapcs-linux`’.

`-mapcs-frame` ¶

  Generate a stack frame that is compliant with the ARM Procedure Call Standard for all functions, even if this is not strictly necessary for correct execution of the code. Specifying `-fomit-frame-pointer` with this option causes the stack frames not to be generated for leaf functions. The default is `-mno-apcs-frame`. This option is deprecated.

`-mapcs` ¶

  This is a synonym for `-mapcs-frame` and is deprecated.

`-mthumb-interwork` ¶

  Generate code that supports calling between the ARM and Thumb instruction sets. Without this option, on pre-v5 architectures, the two instruction sets cannot be reliably used inside one program. The default is `-mno-thumb-interwork`, since slightly larger code is generated when `-mthumb-interwork` is specified. In AAPCS configurations this option is meaningless.

`-msched-prolog` ¶
`-mno-sched-prolog`

  Allow or prevent the reordering of instructions in the function prologue, or the merging of those instruction with the instructions in the function’s body. With `-mno-sched-prolog`, this means that all functions start with a recognizable set of instructions (or in fact one of a choice from a small set of different function prologues), and this information can be used to locate the start of functions inside an executable piece of code. The default is `-msched-prolog`.

`-mfloat-abi=name` ¶

  Specifies which floating-point ABI to use. Permissible values are: ‘`soft`’, ‘`softfp`’ and ‘`hard`’.

  Specifying ‘`soft`’ causes GCC to generate output containing library calls for floating-point operations. ‘`softfp`’ allows the generation of code using hardware floating-point instructions, but still uses the soft-float calling conventions. ‘`hard`’ allows generation of floating-point instructions and uses FPU-specific calling conventions.

  The default depends on the specific target configuration. Note that the hard-float and soft-float ABIs are not link-compatible; you must compile your entire program with the same ABI, and link with a compatible set of libraries.

`-mgeneral-regs-only` ¶

  Generate code which uses only the general-purpose registers. This will prevent the compiler from using floating-point and Advanced SIMD registers but will not impose any restrictions on the assembler.

`-mlittle-endian` ¶

  Generate code for a processor running in little-endian mode. This is the default for all standard configurations.

`-mbig-endian` ¶

  Generate code for a processor running in big-endian mode; the default is to compile code for a little-endian processor.

`-mbe8` ¶
`-mbe32`

  When linking a big-endian image select between BE8 and BE32 formats. The option has no effect for little-endian images and is ignored. The default is dependent on the selected target architecture. For ARMv6 and later architectures the default is BE8, for older architectures the default is BE32. BE32 format has been deprecated by ARM.

`-march=name[+extension…]` ¶

  This specifies the name of the target ARM architecture. GCC uses this name to determine what kind of instructions it can emit when generating assembly code. This option can be used in conjunction with or instead of the `-mcpu=` option.

  Permissible names are: ‘`armv4t`’, ‘`armv5t`’, ‘`armv5te`’, ‘`armv6`’, ‘`armv6j`’, ‘`armv6k`’, ‘`armv6kz`’, ‘`armv6t2`’, ‘`armv6z`’, ‘`armv6zk`’, ‘`armv7`’, ‘`armv7-a`’, ‘`armv7ve`’, ‘`armv8-a`’, ‘`armv8.1-a`’, ‘`armv8.2-a`’, ‘`armv8.3-a`’, ‘`armv8.4-a`’, ‘`armv8.5-a`’, ‘`armv8.6-a`’, ‘`armv9-a`’, ‘`armv7-r`’, ‘`armv8-r`’, ‘`armv6-m`’, ‘`armv6s-m`’, ‘`armv7-m`’, ‘`armv7e-m`’, ‘`armv8-m.base`’, ‘`armv8-m.main`’, ‘`armv8.1-m.main`’, ‘`iwmmxt`’ and ‘`iwmmxt2`’.

  Additionally, the following architectures, which lack support for the Thumb execution state, are recognized but support is deprecated: ‘`armv4`’.

  Many of the architectures support extensions. These can be added by appending ‘`+extension`’ to the architecture name. Extension options are processed in order and capabilities accumulate. An extension will also enable any necessary base extensions upon which it depends. For example, the ‘`+crypto`’ extension will always enable the ‘`+simd`’ extension. The exception to the additive construction is for extensions that are prefixed with ‘`+no…`’: these extensions disable the specified option and any other extensions that may depend on the presence of that extension.

  For example, ‘`-march=armv7-a+simd+nofp+vfpv4`’ is equivalent to writing ‘`-march=armv7-a+vfpv4`’ since the ‘`+simd`’ option is entirely disabled by the ‘`+nofp`’ option that follows it.

  Most extension names are generically named, but have an effect that is dependent upon the architecture to which it is applied. For example, the ‘`+simd`’ option can be applied to both ‘`armv7-a`’ and ‘`armv8-a`’ architectures, but will enable the original ARMv7-A Advanced SIMD (Neon) extensions for ‘`armv7-a`’ and the ARMv8-A variant for ‘`armv8-a`’.

  The table below lists the supported extensions for each architecture. Architectures not mentioned do not support any extensions.

  ‘`armv5te`’
  ‘`armv6`’
  ‘`armv6j`’
  ‘`armv6k`’
  ‘`armv6kz`’
  ‘`armv6t2`’
  ‘`armv6z`’
  ‘`armv6zk`’
    ‘`+fp`’

      The VFPv2 floating-point instructions. The extension ‘`+vfpv2`’ can be used as an alias for this extension.

    ‘`+nofp`’

      Disable the floating-point instructions.

  ‘`armv7`’

    The common subset of the ARMv7-A, ARMv7-R and ARMv7-M architectures.

    ‘`+fp`’

      The VFPv3 floating-point instructions, with 16 double-precision registers. The extension ‘`+vfpv3-d16`’ can be used as an alias for this extension. Note that floating-point is not supported by the base ARMv7-M architecture, but is compatible with both the ARMv7-A and ARMv7-R architectures.

    ‘`+nofp`’

      Disable the floating-point instructions.

  ‘`armv7-a`’
    ‘`+mp`’

      The multiprocessing extension.

    ‘`+sec`’

      The security extension.

    ‘`+fp`’

      The VFPv3 floating-point instructions, with 16 double-precision registers. The extension ‘`+vfpv3-d16`’ can be used as an alias for this extension.

    ‘`+simd`’

      The Advanced SIMD (Neon) v1 and the VFPv3 floating-point instructions. The extensions ‘`+neon`’ and ‘`+neon-vfpv3`’ can be used as aliases for this extension.

    ‘`+vfpv3`’

      The VFPv3 floating-point instructions, with 32 double-precision registers.

    ‘`+vfpv3-d16-fp16`’

      The VFPv3 floating-point instructions, with 16 double-precision registers and the half-precision floating-point conversion operations.

    ‘`+vfpv3-fp16`’

      The VFPv3 floating-point instructions, with 32 double-precision registers and the half-precision floating-point conversion operations.

    ‘`+vfpv4-d16`’

      The VFPv4 floating-point instructions, with 16 double-precision registers.

    ‘`+vfpv4`’

      The VFPv4 floating-point instructions, with 32 double-precision registers.

    ‘`+neon-fp16`’

      The Advanced SIMD (Neon) v1 and the VFPv3 floating-point instructions, with the half-precision floating-point conversion operations.

    ‘`+neon-vfpv4`’

      The Advanced SIMD (Neon) v2 and the VFPv4 floating-point instructions.

    ‘`+nosimd`’

      Disable the Advanced SIMD instructions (does not disable floating point).

    ‘`+nofp`’

      Disable the floating-point and Advanced SIMD instructions.

  ‘`armv7ve`’

    The extended version of the ARMv7-A architecture with support for virtualization.

    ‘`+fp`’

      The VFPv4 floating-point instructions, with 16 double-precision registers. The extension ‘`+vfpv4-d16`’ can be used as an alias for this extension.

    ‘`+simd`’

      The Advanced SIMD (Neon) v2 and the VFPv4 floating-point instructions. The extension ‘`+neon-vfpv4`’ can be used as an alias for this extension.

    ‘`+vfpv3-d16`’

      The VFPv3 floating-point instructions, with 16 double-precision registers.

    ‘`+vfpv3`’

      The VFPv3 floating-point instructions, with 32 double-precision registers.

    ‘`+vfpv3-d16-fp16`’

      The VFPv3 floating-point instructions, with 16 double-precision registers and the half-precision floating-point conversion operations.

    ‘`+vfpv3-fp16`’

      The VFPv3 floating-point instructions, with 32 double-precision registers and the half-precision floating-point conversion operations.

    ‘`+vfpv4-d16`’

      The VFPv4 floating-point instructions, with 16 double-precision registers.

    ‘`+vfpv4`’

      The VFPv4 floating-point instructions, with 32 double-precision registers.

    ‘`+neon`’

      The Advanced SIMD (Neon) v1 and the VFPv3 floating-point instructions. The extension ‘`+neon-vfpv3`’ can be used as an alias for this extension.

    ‘`+neon-fp16`’

      The Advanced SIMD (Neon) v1 and the VFPv3 floating-point instructions, with the half-precision floating-point conversion operations.

    ‘`+nosimd`’

      Disable the Advanced SIMD instructions (does not disable floating point).

    ‘`+nofp`’

      Disable the floating-point and Advanced SIMD instructions.

  ‘`armv8-a`’
    ‘`+crc`’

      The Cyclic Redundancy Check (CRC) instructions.

    ‘`+simd`’

      The ARMv8-A Advanced SIMD and floating-point instructions.

    ‘`+crypto`’

      The cryptographic instructions.

    ‘`+nocrypto`’

      Disable the cryptographic instructions.

    ‘`+nofp`’

      Disable the floating-point, Advanced SIMD and cryptographic instructions.

    ‘`+sb`’

      Speculation Barrier Instruction.

    ‘`+predres`’

      Execution and Data Prediction Restriction Instructions.

  ‘`armv8.1-a`’
    ‘`+simd`’

      The ARMv8.1-A Advanced SIMD and floating-point instructions.

    ‘`+crypto`’

      The cryptographic instructions. This also enables the Advanced SIMD and floating-point instructions.

    ‘`+nocrypto`’

      Disable the cryptographic instructions.

    ‘`+nofp`’

      Disable the floating-point, Advanced SIMD and cryptographic instructions.

    ‘`+sb`’

      Speculation Barrier Instruction.

    ‘`+predres`’

      Execution and Data Prediction Restriction Instructions.

  ‘`armv8.2-a`’
  ‘`armv8.3-a`’
    ‘`+fp16`’

      The half-precision floating-point data processing instructions. This also enables the Advanced SIMD and floating-point instructions.

    ‘`+fp16fml`’

      The half-precision floating-point fmla extension. This also enables the half-precision floating-point extension and Advanced SIMD and floating-point instructions.

    ‘`+simd`’

      The ARMv8.1-A Advanced SIMD and floating-point instructions.

    ‘`+crypto`’

      The cryptographic instructions. This also enables the Advanced SIMD and floating-point instructions.

    ‘`+dotprod`’

      Enable the Dot Product extension. This also enables Advanced SIMD instructions.

    ‘`+nocrypto`’

      Disable the cryptographic extension.

    ‘`+nofp`’

      Disable the floating-point, Advanced SIMD and cryptographic instructions.

    ‘`+sb`’

      Speculation Barrier Instruction.

    ‘`+predres`’

      Execution and Data Prediction Restriction Instructions.

    ‘`+i8mm`’

      8-bit Integer Matrix Multiply instructions. This also enables Advanced SIMD and floating-point instructions.

    ‘`+bf16`’

      Brain half-precision floating-point instructions. This also enables Advanced SIMD and floating-point instructions.

  ‘`armv8.4-a`’
    ‘`+fp16`’

      The half-precision floating-point data processing instructions. This also enables the Advanced SIMD and floating-point instructions as well as the Dot Product extension and the half-precision floating-point fmla extension.

    ‘`+simd`’

      The ARMv8.3-A Advanced SIMD and floating-point instructions as well as the Dot Product extension.

    ‘`+crypto`’

      The cryptographic instructions. This also enables the Advanced SIMD and floating-point instructions as well as the Dot Product extension.

    ‘`+nocrypto`’

      Disable the cryptographic extension.

    ‘`+nofp`’

      Disable the floating-point, Advanced SIMD and cryptographic instructions.

    ‘`+sb`’

      Speculation Barrier Instruction.

    ‘`+predres`’

      Execution and Data Prediction Restriction Instructions.

    ‘`+i8mm`’

      8-bit Integer Matrix Multiply instructions. This also enables Advanced SIMD and floating-point instructions.

    ‘`+bf16`’

      Brain half-precision floating-point instructions. This also enables Advanced SIMD and floating-point instructions.

  ‘`armv8.5-a`’
    ‘`+fp16`’

      The half-precision floating-point data processing instructions. This also enables the Advanced SIMD and floating-point instructions as well as the Dot Product extension and the half-precision floating-point fmla extension.

    ‘`+simd`’

      The ARMv8.3-A Advanced SIMD and floating-point instructions as well as the Dot Product extension.

    ‘`+crypto`’

      The cryptographic instructions. This also enables the Advanced SIMD and floating-point instructions as well as the Dot Product extension.

    ‘`+nocrypto`’

      Disable the cryptographic extension.

    ‘`+nofp`’

      Disable the floating-point, Advanced SIMD and cryptographic instructions.

    ‘`+i8mm`’

      8-bit Integer Matrix Multiply instructions. This also enables Advanced SIMD and floating-point instructions.

    ‘`+bf16`’

      Brain half-precision floating-point instructions. This also enables Advanced SIMD and floating-point instructions.

  ‘`armv8.6-a`’
    ‘`+fp16`’

      The half-precision floating-point data processing instructions. This also enables the Advanced SIMD and floating-point instructions as well as the Dot Product extension and the half-precision floating-point fmla extension.

    ‘`+simd`’

      The ARMv8.3-A Advanced SIMD and floating-point instructions as well as the Dot Product extension.

    ‘`+crypto`’

      The cryptographic instructions. This also enables the Advanced SIMD and floating-point instructions as well as the Dot Product extension.

    ‘`+nocrypto`’

      Disable the cryptographic extension.

    ‘`+nofp`’

      Disable the floating-point, Advanced SIMD and cryptographic instructions.

    ‘`+i8mm`’

      8-bit Integer Matrix Multiply instructions. This also enables Advanced SIMD and floating-point instructions.

    ‘`+bf16`’

      Brain half-precision floating-point instructions. This also enables Advanced SIMD and floating-point instructions.

  ‘`armv7-r`’
    ‘`+fp.sp`’

      The single-precision VFPv3 floating-point instructions. The extension ‘`+vfpv3xd`’ can be used as an alias for this extension.

    ‘`+fp`’

      The VFPv3 floating-point instructions with 16 double-precision registers. The extension +vfpv3-d16 can be used as an alias for this extension.

    ‘`+vfpv3xd-d16-fp16`’

      The single-precision VFPv3 floating-point instructions with 16 double-precision registers and the half-precision floating-point conversion operations.

    ‘`+vfpv3-d16-fp16`’

      The VFPv3 floating-point instructions with 16 double-precision registers and the half-precision floating-point conversion operations.

    ‘`+nofp`’

      Disable the floating-point extension.

    ‘`+idiv`’

      The ARM-state integer division instructions.

    ‘`+noidiv`’

      Disable the ARM-state integer division extension.

  ‘`armv7e-m`’
    ‘`+fp`’

      The single-precision VFPv4 floating-point instructions.

    ‘`+fpv5`’

      The single-precision FPv5 floating-point instructions.

    ‘`+fp.dp`’

      The single- and double-precision FPv5 floating-point instructions.

    ‘`+nofp`’

      Disable the floating-point extensions.

  ‘`armv8.1-m.main`’
    ‘`+dsp`’

      The DSP instructions.

    ‘`+mve`’

      The M-Profile Vector Extension (MVE) integer instructions.

    ‘`+mve.fp`’

      The M-Profile Vector Extension (MVE) integer and single precision floating-point instructions.

    ‘`+fp`’

      The single-precision floating-point instructions.

    ‘`+fp.dp`’

      The single- and double-precision floating-point instructions.

    ‘`+nofp`’

      Disable the floating-point extension.

    ‘`+cdecp0, +cdecp1, ... , +cdecp7`’

      Enable the Custom Datapath Extension (CDE) on selected coprocessors according to the numbers given in the options in the range 0 to 7.

    ‘`+pacbti`’

      Enable the Pointer Authentication and Branch Target Identification Extension.

  ‘`armv8-m.main`’
    ‘`+dsp`’

      The DSP instructions.

    ‘`+nodsp`’

      Disable the DSP extension.

    ‘`+fp`’

      The single-precision floating-point instructions.

    ‘`+fp.dp`’

      The single- and double-precision floating-point instructions.

    ‘`+nofp`’

      Disable the floating-point extension.

    ‘`+cdecp0, +cdecp1, ... , +cdecp7`’

      Enable the Custom Datapath Extension (CDE) on selected coprocessors according to the numbers given in the options in the range 0 to 7.

  ‘`armv8-r`’
    ‘`+crc`’

      The Cyclic Redundancy Check (CRC) instructions.

    ‘`+fp.sp`’

      The single-precision FPv5 floating-point instructions.

    ‘`+simd`’

      The ARMv8-A Advanced SIMD and floating-point instructions.

    ‘`+crypto`’

      The cryptographic instructions.

    ‘`+nocrypto`’

      Disable the cryptographic instructions.

    ‘`+nofp`’

      Disable the floating-point, Advanced SIMD and cryptographic instructions.

  `-march=native` causes the compiler to auto-detect the architecture of the build computer. At present, this feature is only supported on GNU/Linux, and not all architectures are recognized. If the auto-detect is unsuccessful the option has no effect.

  `-march=unset` causes the compiler to ignore any `-march=…` options that appear earlier on the command line and behave as if the option was never passed. This is useful to avoid warnings about conflicting CPU and architecture options when the two produce different architecture specifications.

`-mtune=name` ¶

  This option specifies the name of the target ARM processor for which GCC should tune the performance of the code. For some ARM implementations better performance can be obtained by using this option. Permissible names are: ‘`arm7tdmi`’, ‘`arm7tdmi-s`’, ‘`arm710t`’, ‘`arm720t`’, ‘`arm740t`’, ‘`strongarm`’, ‘`strongarm110`’, ‘`strongarm1100`’, ‘`strongarm1110`’, ‘`arm8`’, ‘`arm810`’, ‘`arm9`’, ‘`arm9e`’, ‘`arm920`’, ‘`arm920t`’, ‘`arm922t`’, ‘`arm946e-s`’, ‘`arm966e-s`’, ‘`arm968e-s`’, ‘`arm926ej-s`’, ‘`arm940t`’, ‘`arm9tdmi`’, ‘`arm10tdmi`’, ‘`arm1020t`’, ‘`arm1026ej-s`’, ‘`arm10e`’, ‘`arm1020e`’, ‘`arm1022e`’, ‘`arm1136j-s`’, ‘`arm1136jf-s`’, ‘`mpcore`’, ‘`mpcorenovfp`’, ‘`arm1156t2-s`’, ‘`arm1156t2f-s`’, ‘`arm1176jz-s`’, ‘`arm1176jzf-s`’, ‘`generic-armv7-a`’, ‘`cortex-a5`’, ‘`cortex-a7`’, ‘`cortex-a8`’, ‘`cortex-a9`’, ‘`cortex-a12`’, ‘`cortex-a15`’, ‘`cortex-a17`’, ‘`cortex-a32`’, ‘`cortex-a35`’, ‘`cortex-a53`’, ‘`cortex-a55`’, ‘`cortex-a57`’, ‘`cortex-a72`’, ‘`cortex-a73`’, ‘`cortex-a75`’, ‘`cortex-a76`’, ‘`cortex-a76ae`’, ‘`cortex-a77`’, ‘`cortex-a78`’, ‘`cortex-a78ae`’, ‘`cortex-a78c`’, ‘`cortex-a710`’, ‘`ares`’, ‘`cortex-r4`’, ‘`cortex-r4f`’, ‘`cortex-r5`’, ‘`cortex-r7`’, ‘`cortex-r8`’, ‘`cortex-r52`’, ‘`cortex-r52plus`’, ‘`cortex-m0`’, ‘`cortex-m0plus`’, ‘`cortex-m1`’, ‘`cortex-m3`’, ‘`cortex-m4`’, ‘`cortex-m7`’, ‘`cortex-m23`’, ‘`cortex-m33`’, ‘`cortex-m35p`’, ‘`cortex-m52`’, ‘`cortex-m55`’, ‘`cortex-m85`’, ‘`cortex-x1`’, ‘`cortex-x1c`’, ‘`cortex-m1.small-multiply`’, ‘`cortex-m0.small-multiply`’, ‘`cortex-m0plus.small-multiply`’, ‘`exynos-m1`’, ‘`marvell-pj4`’, ‘`neoverse-n1`’, ‘`neoverse-n2`’, ‘`neoverse-v1`’, ‘`xscale`’, ‘`iwmmxt`’, ‘`iwmmxt2`’, ‘`ep9312`’, ‘`fa526`’, ‘`fa626`’, ‘`fa606te`’, ‘`fa626te`’, ‘`fmp626`’, ‘`fa726te`’, ‘`star-mc1`’, ‘`star-mc3`’, ‘`xgene1`’.

  Additionally, this option can specify that GCC should tune the performance of the code for a big.LITTLE system. Permissible names are: ‘`cortex-a15.cortex-a7`’, ‘`cortex-a17.cortex-a7`’, ‘`cortex-a57.cortex-a53`’, ‘`cortex-a72.cortex-a53`’, ‘`cortex-a72.cortex-a35`’, ‘`cortex-a73.cortex-a53`’, ‘`cortex-a75.cortex-a55`’, ‘`cortex-a76.cortex-a55`’.

  `-mtune=generic-arch` specifies that GCC should tune the performance for a blend of processors within architecture arch. The aim is to generate code that run well on the current most popular processors, balancing between optimizations that benefit some CPUs in the range, and avoiding performance pitfalls of other CPUs. The effects of this option may change in future GCC versions as CPU models come and go.

  `-mtune` permits the same extension options as `-mcpu`, but the extension options do not affect the tuning of the generated code.

  `-mtune=native` causes the compiler to auto-detect the CPU of the build computer. At present, this feature is only supported on GNU/Linux, and not all architectures are recognized. If the auto-detect is unsuccessful the option has no effect.

`-mcpu=name[+extension…]` ¶

  This specifies the name of the target ARM processor. GCC uses this name to derive the name of the target ARM architecture (as if specified by `-march`) and the ARM processor type for which to tune for performance (as if specified by `-mtune`). Where this option is used in conjunction with `-march` or `-mtune`, those options take precedence over the appropriate part of this option.

  Many of the supported CPUs implement optional architectural extensions. Where this is so the architectural extensions are normally enabled by default. If implementations that lack the extension exist, then the extension syntax can be used to disable those extensions that have been omitted. For floating-point and Advanced SIMD (Neon) instructions, the settings of the options `-mfloat-abi` and `-mfpu` must also be considered: floating-point and Advanced SIMD instructions will only be used if `-mfloat-abi` is not set to ‘`soft`’; and any setting of `-mfpu` other than ‘`auto`’ will override the available floating-point and SIMD extension instructions.

  For example, ‘`cortex-a9`’ can be found in three major configurations: integer only, with just a floating-point unit or with floating-point and Advanced SIMD. The default is to enable all the instructions, but the extensions ‘`+nosimd`’ and ‘`+nofp`’ can be used to disable just the SIMD or both the SIMD and floating-point instructions respectively.

  Permissible names for this option are the same as those for `-mtune`.

  The following extension options are common to the listed CPUs:

  ‘`+nodsp`’

    Disable the DSP instructions on ‘`cortex-m33`’, ‘`cortex-m35p`’, ‘`cortex-m52`’, ‘`cortex-m55`’, ‘`cortex-m85`’ and ‘`star-mc3`’. Also disable the M-Profile Vector Extension (MVE) integer and single precision floating-point instructions on ‘`cortex-m52`’, ‘`cortex-m55`’, ‘`cortex-m85`’ and ‘`star-mc3`’.

  ‘`+nopacbti`’

    Disable the Pointer Authentication and Branch Target Identification Extension on ‘`cortex-m52`’, ‘`cortex-m85`’ and ‘`star-mc3`’.

  ‘`+nomve`’

    Disable the M-Profile Vector Extension (MVE) integer and single precision floating-point instructions on ‘`cortex-m52`’, ‘`cortex-m55`’, ‘`cortex-m85`’ and ‘`star-mc3`’.

  ‘`+nomve.fp`’

    Disable the M-Profile Vector Extension (MVE) single precision floating-point instructions on ‘`cortex-m52`’, ‘`cortex-m55`’, ‘`cortex-m85`’ and ‘`star-mc3`’.

  ‘`+cdecp0, +cdecp1, ... , +cdecp7`’

    Enable the Custom Datapath Extension (CDE) on selected coprocessors according to the numbers given in the options in the range 0 to 7 on ‘`cortex-m52`’, ‘`cortex-m55`’, ‘`cortex-m85`’, ‘`star-mc1`’ and ‘`star-mc3`’.

  ‘`+nofp`’

    Disables the floating-point instructions on ‘`arm9e`’, ‘`arm946e-s`’, ‘`arm966e-s`’, ‘`arm968e-s`’, ‘`arm10e`’, ‘`arm1020e`’, ‘`arm1022e`’, ‘`arm926ej-s`’, ‘`arm1026ej-s`’, ‘`cortex-r5`’, ‘`cortex-r7`’, ‘`cortex-r8`’, ‘`cortex-m4`’, ‘`cortex-m7`’, ‘`cortex-m33`’, ‘`cortex-m35p`’, ‘`cortex-m52`’, ‘`cortex-m55`’, ‘`cortex-m85`’ and ‘`star-mc3`’. Disables the floating-point and SIMD instructions on ‘`generic-armv7-a`’, ‘`cortex-a5`’, ‘`cortex-a7`’, ‘`cortex-a8`’, ‘`cortex-a9`’, ‘`cortex-a12`’, ‘`cortex-a15`’, ‘`cortex-a17`’, ‘`cortex-a15.cortex-a7`’, ‘`cortex-a17.cortex-a7`’, ‘`cortex-a32`’, ‘`cortex-a35`’, ‘`cortex-a53`’ and ‘`cortex-a55`’.

  ‘`+nofp.dp`’

    Disables the double-precision component of the floating-point instructions on ‘`cortex-r5`’, ‘`cortex-r7`’, ‘`cortex-r8`’, ‘`cortex-r52`’, ‘`cortex-r52plus`’ and ‘`cortex-m7`’.

  ‘`+nosimd`’

    Disables the SIMD (but not floating-point) instructions on ‘`generic-armv7-a`’, ‘`cortex-a5`’, ‘`cortex-a7`’ and ‘`cortex-a9`’.

  ‘`+crypto`’

    Enables the cryptographic instructions on ‘`cortex-a32`’, ‘`cortex-a35`’, ‘`cortex-a53`’, ‘`cortex-a55`’, ‘`cortex-a57`’, ‘`cortex-a72`’, ‘`cortex-a73`’, ‘`cortex-a75`’, ‘`exynos-m1`’, ‘`xgene1`’, ‘`cortex-a57.cortex-a53`’, ‘`cortex-a72.cortex-a53`’, ‘`cortex-a73.cortex-a35`’, ‘`cortex-a73.cortex-a53`’ and ‘`cortex-a75.cortex-a55`’.

  Additionally the ‘`generic-armv7-a`’ pseudo target defaults to VFPv3 with 16 double-precision registers. It supports the following extension options: ‘`mp`’, ‘`sec`’, ‘`vfpv3-d16`’, ‘`vfpv3`’, ‘`vfpv3-d16-fp16`’, ‘`vfpv3-fp16`’, ‘`vfpv4-d16`’, ‘`vfpv4`’, ‘`neon`’, ‘`neon-vfpv3`’, ‘`neon-fp16`’, ‘`neon-vfpv4`’. The meanings are the same as for the extensions to `-march=armv7-a`.

  `-mcpu=generic-arch` is also permissible, and is equivalent to `-march=arch -mtune=generic-arch`. See `-mtune` for more information.

  `-mcpu=native` causes the compiler to auto-detect the CPU of the build computer. At present, this feature is only supported on GNU/Linux, and not all architectures are recognized. If the auto-detect is unsuccessful the option has no effect.

  `-mcpu=unset` causes the compiler to ignore any `-mcpu=…` options that appear earlier on the command line and behave as if the option was never passed. This is useful to avoid warnings about conflicting CPU and architecture options when the two produce different architecture specifications.

`-mfpu=name` ¶

  This specifies what floating-point hardware (or hardware emulation) is available on the target. Permissible names are: ‘`auto`’, ‘`vfpv2`’, ‘`vfpv3`’, ‘`vfpv3-fp16`’, ‘`vfpv3-d16`’, ‘`vfpv3-d16-fp16`’, ‘`vfpv3xd`’, ‘`vfpv3xd-fp16`’, ‘`neon-vfpv3`’, ‘`neon-fp16`’, ‘`vfpv4`’, ‘`vfpv4-d16`’, ‘`fpv4-sp-d16`’, ‘`neon-vfpv4`’, ‘`fpv5-d16`’, ‘`fpv5-sp-d16`’, ‘`fp-armv8`’, ‘`neon-fp-armv8`’ and ‘`crypto-neon-fp-armv8`’. Note that ‘`neon`’ is an alias for ‘`neon-vfpv3`’ and ‘`vfp`’ is an alias for ‘`vfpv2`’.

  The setting ‘`auto`’ is the default and is special. It causes the compiler to select the floating-point and Advanced SIMD instructions based on the settings of `-mcpu` and `-march`.

  If the selected floating-point hardware includes the NEON extension (e.g. `-mfpu=neon`), note that floating-point operations are not generated by GCC’s auto-vectorization pass unless `-funsafe-math-optimizations` is also specified. This is because NEON hardware does not fully implement the IEEE 754 standard for floating-point arithmetic (in particular denormal values are treated as zero), so the use of NEON instructions may lead to a loss of precision.

  You can also set the fpu name at function level by using the `target("fpu=")` function attributes (see ARM Attributes) or pragmas (see Function Specific Option Pragmas).

`-mfp16-format=name` ¶

  Specify the format of the `__fp16` half-precision floating-point type. Permissible names are ‘`none`’, ‘`ieee`’, and ‘`alternative`’; the default is ‘`none`’, in which case the `__fp16` type is not defined. See Half-Precision Floating Point, for more information.

`-mstructure-size-boundary=n` ¶

  The sizes of all structures and unions are rounded up to a multiple of the number of bits set by this option. Permissible values are 8, 32 and 64. The default value varies for different toolchains. For the COFF targeted toolchain the default value is 8. A value of 64 is only allowed if the underlying ABI supports it.

  Specifying a larger number can produce faster, more efficient code, but can also increase the size of the program. Different values are potentially incompatible. Code compiled with one value cannot necessarily expect to work with code or libraries compiled with another value, if they exchange information using structures or unions.

  This option is deprecated.

`-mabort-on-noreturn` ¶

  Generate a call to the function `abort` at the end of a `noreturn` function. It is executed if the function tries to return.

`-mlong-calls` ¶
`-mno-long-calls`

  Tells the compiler to perform function calls by first loading the address of the function into a register and then performing a subroutine call on this register. This switch is needed if the target function lies outside of the 64-megabyte addressing range of the offset-based version of subroutine call instruction.

  Even if this switch is enabled, not all function calls are turned into long calls. The heuristic is that static functions, functions that have the `short_call` attribute, functions that are inside the scope of a `#pragma no_long_calls` directive, and functions whose definitions have already been compiled within the current compilation unit are not turned into long calls. The exceptions to this rule are that weak function definitions, functions with the `long_call` attribute or the `section` attribute, and functions that are within the scope of a `#pragma long_calls` directive are always turned into long calls.

  This feature is not enabled by default. Specifying `-mno-long-calls` restores the default behavior, as does placing the function calls within the scope of a `#pragma long_calls_off` directive. Note these switches have no effect on how the compiler generates code to handle function calls via function pointers.

`-msingle-pic-base` ¶

  Treat the register used for PIC addressing as read-only, rather than loading it in the prologue for each function. The runtime system is responsible for initializing this register with an appropriate value before execution begins.

`-mpic-register=reg` ¶

  Specify the register to be used for PIC addressing. For standard PIC base case, the default is any suitable register determined by compiler. For single PIC base case, the default is ‘`R9`’ if target is EABI based or stack-checking is enabled, otherwise the default is ‘`R10`’.

`-mpic-data-is-text-relative` ¶

  Assume that the displacement between the text and data segments is fixed at static link time. This permits using PC-relative addressing operations to access data known to be in the data segment. For non-VxWorks RTP targets, this option is enabled by default. When disabled on such targets, it will enable `-msingle-pic-base` by default.

`-mpoke-function-name` ¶

  Write the name of each function into the text section, directly preceding the function prologue. The generated code is similar to this:

           t0
               .ascii "arm_poke_function_name", 0
               .align
           t1
               .word 0xff000000 + (t1 - t0)
           arm_poke_function_name
               mov     ip, sp
               stmfd   sp!, {fp, ip, lr, pc}
               sub     fp, ip, #4

  When performing a stack backtrace, code can inspect the value of `pc` stored at `fp + 0`. If the trace function then looks at location `pc - 12` and the top 8 bits are set, then we know that there is a function name embedded immediately preceding this location and has length `((pc[-3]) & 0xff000000)`.

`-mthumb` ¶
`-marm`

  Select between generating code that executes in ARM and Thumb states. The default for most configurations is to generate code that executes in ARM state, but the default can be changed by configuring GCC with the `--with-mode=`state configure option.

  You can also override the ARM and Thumb mode for each function by using the `target("thumb")` and `target("arm")` function attributes (see ARM Attributes) or pragmas (see Function Specific Option Pragmas).

`-mtpcs-frame` ¶

  Generate a stack frame that is compliant with the Thumb Procedure Call Standard for all non-leaf functions. (A leaf function is one that does not call any other functions.) The default is `-mno-tpcs-frame`.

`-mtpcs-leaf-frame` ¶

  Generate a stack frame that is compliant with the Thumb Procedure Call Standard for all leaf functions. (A leaf function is one that does not call any other functions.) The default is `-mno-apcs-leaf-frame`.

`-mcallee-super-interworking` ¶

  Gives all externally visible functions in the file being compiled an ARM instruction set header which switches to Thumb mode before executing the rest of the function. This allows these functions to be called from non-interworking code. This option is not valid in AAPCS configurations because interworking is enabled by default.

`-mcaller-super-interworking` ¶

  Allows calls via function pointers (including virtual functions) to execute correctly regardless of whether the target code has been compiled for interworking or not. There is a small overhead in the cost of executing a function pointer if this option is enabled. This option is not valid in AAPCS configurations because interworking is enabled by default.

`-mtp=name` ¶

  Specify the access model for the thread local storage pointer. The model ‘`soft`’ generates calls to `__aeabi_read_tp`. Other accepted models are ‘`tpidrurw`’, ‘`tpidruro`’ and ‘`tpidrprw`’ which fetch the thread pointer from the corresponding system register directly (supported from the arm6k architecture and later). These system registers are accessed through the CP15 co-processor interface and the argument ‘`cp15`’ is also accepted as a convenience alias of ‘`tpidruro`’. The argument ‘`auto`’ uses the best available method for the selected processor. The default setting is ‘`auto`’.

`-mtls-dialect=dialect` ¶

  Specify the dialect to use for accessing thread local storage. Two dialects are supported—‘`gnu`’ and ‘`gnu2`’. The ‘`gnu`’ dialect selects the original GNU scheme for supporting local and global dynamic TLS models. The ‘`gnu2`’ dialect selects the GNU descriptor scheme, which provides better performance for shared libraries. The GNU descriptor scheme is compatible with the original scheme, but does require new assembler, linker and library support. Initial and local exec TLS models are unaffected by this option and always use the original scheme.

`-mword-relocations` ¶

  Only generate absolute relocations on word-sized values (i.e. R_ARM_ABS32). This is enabled by default on targets (uClinux, SymbianOS) where the runtime loader imposes this restriction, and when `-fpic` or `-fPIC` is specified. This option conflicts with `-mslow-flash-data`.

`-mfix-cortex-m3-ldrd` ¶

  Some Cortex-M3 cores can cause data corruption when `ldrd` instructions with overlapping destination and base registers are used. This option avoids generating these instructions. This option is enabled by default when `-mcpu=cortex-m3` is specified.

`-mfix-cortex-a57-aes-1742098` ¶
`-mno-fix-cortex-a57-aes-1742098`
`-mfix-cortex-a72-aes-1655431`
`-mno-fix-cortex-a72-aes-1655431`

  Enable (disable) mitigation for an erratum on Cortex-A57 and Cortex-A72 that affects the AES cryptographic instructions. This option is enabled by default when either `-mcpu=cortex-a57` or `-mcpu=cortex-a72` is specified.

`-munaligned-access` ¶
`-mno-unaligned-access`

  Enables (or disables) reading and writing of 16- and 32- bit values from addresses that are not 16- or 32- bit aligned. By default unaligned access is disabled for all pre-ARMv6, all ARMv6-M and for ARMv8-M Baseline architectures, and enabled for all other architectures. If unaligned access is not enabled then words in packed data structures are accessed a byte at a time.

  The ARM attribute `Tag_CPU_unaligned_access` is set in the generated object file to either true or false, depending upon the setting of this option. If unaligned access is enabled then the preprocessor symbol `__ARM_FEATURE_UNALIGNED` is also defined.

`-mslow-flash-data` ¶

  Assume loading data from flash is slower than fetching instruction. Therefore literal load is minimized for better performance. This option is only supported when compiling for ARMv7 M-profile and off by default. It conflicts with `-mword-relocations`.

`-masm-syntax-unified` ¶

  Assume inline assembler is using unified asm syntax. The default is currently off which implies divided syntax. This option has no impact on Thumb2. However, this may change in future releases of GCC. Divided syntax should be considered deprecated.

`-mrestrict-it` ¶

  Restricts generation of IT blocks to conform to the rules of ARMv8-A. IT blocks can only contain a single 16-bit instruction from a select set of instructions. This option is on by default for ARMv8-A Thumb mode.

`-mpure-code` ¶

  Do not allow constant data to be placed in code sections. Additionally, when compiling for ELF object format give all text sections the ELF processor-specific section attribute `SHF_ARM_PURECODE`. This option is only available when generating non-pic code for M-profile targets.

`-mcmse` ¶

  Generate secure code as per the "ARMv8-M Security Extensions: Requirements on Development Tools Engineering Specification", which can be found on https://developer.arm.com/documentation/ecm0359818/latest/.

`-mfix-cmse-cve-2021-35465` ¶

  Mitigate against a potential security issue with the `VLLDM` instruction in some M-profile devices when using CMSE (CVE-2021-35465). This option is enabled by default when the option `-mcpu=` is used with `cortex-m33`, `cortex-m35p`, `cortex-m55`, `cortex-m85` or `star-mc1`. The option `-mno-fix-cmse-cve-2021-35465` can be used to disable the mitigation.

`-mstack-protector-guard=guard` ¶
`-mstack-protector-guard-offset=offset`

  Generate stack protection code using canary at guard. Supported locations are ‘`global`’ for a global canary or ‘`tls`’ for a canary accessible via the TLS register. The option `-mstack-protector-guard-offset=` is for use with `-fstack-protector-guard=tls` and not for use in user-land code.

`-mfdpic` ¶
`-mno-fdpic`

  Select the FDPIC ABI, which uses 64-bit function descriptors to represent pointers to functions. When the compiler is configured for `arm-*-uclinuxfdpiceabi` targets, this option is on by default and implies `-fPIE` if none of the PIC/PIE-related options is provided. On other targets, it only enables the FDPIC-specific code generation features, and the user should explicitly provide the PIC/PIE-related options as needed.

  Note that static linking is not supported because it would still involve the dynamic linker when the program self-relocates. If such behavior is acceptable, use -static and -Wl,-dynamic-linker options.

  The opposite `-mno-fdpic` option is useful (and required) to build the Linux kernel using the same (`arm-*-uclinuxfdpiceabi`) toolchain as the one used to build the userland programs.

`-mbranch-protection=features` ¶

  Enable branch protection features (armv8.1-m.main only).

  features can have one of the following forms:

  ‘`none`’ generates code without branch protection or return address signing.

  ‘`standard`’ generates code with all branch protection features enabled at their standard level.

  ‘`pac-ret`’ generates code with return address signing set to its standard level, which is to sign all functions that save the return address to memory.

  ‘`pac-ret+leaf`’ extends the ‘`pac-ret`’ signing to include leaf functions even if they do not write the return address to memory.

  ‘`bti`’ adds landing-pad instructions at the permitted targets of indirect branch instructions.

  If support for the ‘`+pacbti`’ architecture extension is not enabled (e.g. via `-march=`), then all branch protection and return address signing operations are constrained to use only the instructions defined in the architectural-NOP space. The generated code remains backwards-compatible with earlier versions of the architecture, but the additional security can be enabled at run time on processors that support the ‘`PACBTI`’ extension.

  Branch target enforcement using BTI can only be enabled at runtime if all code in the application has been compiled with at least ‘`-mbranch-protection=bti`’.

  Any setting other than ‘`none`’ is supported only on armv8-m.main or later.

  The default is to generate code without branch protection or return address signing.

`-mvectorize-with-neon-quad` ¶
`-mvectorize-with-neon-double`

  Control whether vectorization uses NEON quad-word or double-word registers. The default is `-mvectorize-with-neon-quad`.