Predefined macros
This topic documents the predefined macros of the ARM compiler.
Table 28 lists the macro names predefined by the ARM compiler for C and C++. Where the value field is empty, the symbol is only defined. Table 28. Predefined macros Name__arm__
ValueWhen defined-Always defined for the ARM compiler, even when you specify the --thumb option. See also __ARMCC_VERSION.
__ARMCC_VERSION
ver
Always defined. It is a decimal number, and is guaranteed to increase between releases. The format is PVVbbbb where:
P is the major version VV is the minor version bbbb is the build number.
Note
Use this macro to distinguish between ARM Compiler 4.1 or later, and other tools that define __arm__.
__APCS_INTERWORK
-When you specify the --apcs /interwork option or set the CPU architecture to ARMv5T or later.
When you specify the --apcs /ropi option. When you specify the --apcs /rwpi option. When you specify the --apcs /fpic option. In C++ compiler mode, to specify that array new and delete are enabled.
Always defined. Similar to __FILE__, but indicates the primary source file rather than the current one (that is, when the current file is an included file).
If compiling for a big-endian target.
In C++ compiler mode, to specify that bool is a keyword.
In C++ compiler mode.
__APCS_ROPI__APCS_RWPI__APCS_FPIC__ARRAY_OPERATORS__BASE_FILE__
----name
__BIG_ENDIAN_BOOL__cplusplus
---
mk:@MSITStore:C:\\Keil_v5\\ARM\\HLP\\armccref.chm::/armccref_babjf...2014-6-20
Compiler Reference Guide: Predefined macrosPage 2of 6
__CC_ARM
1date---
Always set to 1 for the ARM compiler, even when you specify the --thumb option. Always defined.Always defined.
In C++ mode when you specify the --using_std option.
Always set to an integer value that represents the version number of the Edison Design Group (EDG) front-end. For example, version 3.8 is represented as 308.
The version number of the EDG front-end does not necessarily match the version number of the ARM compiler toolchain.
__DATE____EDG__
__EDG_IMPLICIT_USING_STD
__EDG_VERSION__
__EXCEPTIONS
1-name----
In C++ mode when you specify the --exceptions option.
When you specify the --signed_chars option (used by CHAR_MIN and CHAR_MAX). Always defined as a string literal.
When you specify the --fpmode=fast option. When you specify the --fpmode=ieee_full or --fpmode=ieee_fixed options.
When you specify the --fpmode=ieee_full option.
When you specify the --fpmode=ieee_full, --fpmode=ieee_fixed, or --fpmode=ieee_no_fenv options.
When you specify the --fpmode=ieee_full option.
When you specify the --implicit_include option.
Always set. It is the source line number of the line of code containing this macro.
Contains the filename part of the value of __FILE__.
When you explicitly or implicitly use the --multifile option.[a]
Always set to 2 by default, unless you change the optimization level using the -Onum option.[a]
__FEATURE_SIGNED_CHAR
__FILE____FP_FAST
__FP_FENV_EXCEPTIONS
__FP_FENV_ROUNDING
__FP_IEEE
__FP_INEXACT_EXCEPTION
--nummod-num
__IMPLICIT_INCLUDE
__LINE____MODULE__
__MULTIFILE
__OPTIMISE_LEVEL
mk:@MSITStore:C:\\Keil_v5\\ARM\\HLP\\armccref.chm::/armccref_babjf...2014-6-20
Compiler Reference Guide: Predefined macrosPage 3of 6
__OPTIMISE_SPACE__OPTIMISE_TIME__PLACEMENT_DELETE
---
When you specify the -Ospace option. When you specify the -Otime option.
In C++ mode to specify that placement delete (that is, an operator delete corresponding to a placement operator new, to be called if the constructor throws an exception) is enabled. This is only relevant when using exceptions.In C++ mode when RTTI is enabled.
For sizeof(int), but available in preprocessor expressions.
For sizeof(long), but available in preprocessor expressions.
For sizeof(void *), but available in preprocessor expressions.
If compiling to use the software floating-point calling standard and library. Set when you specify the --fpu=softvfp option for ARM or Thumb, or when you specify --fpu=softvfp+vfpv2 for Thumb. In all compiler modes.Standard version information.
When you specify the --strict option. Support for signalling NaNs when you specify --fpmode=ieee_fixed or --fpmode=ieee_full.The number of the ARM base architecture of the target CPU irrespective of whether the compiler is compiling for ARM or Thumb. For possible values of __TARGET_ARCH_ARM in
relation to the ARM architecture versions, see Table 29.
The number of the Thumb base architecture of the target CPU irrespective of whether the compiler is compiling for ARM or Thumb. The value is defined as zero if the target does not support Thumb. For possible values of
__TARGET_ARCH_THUMB in relation to the ARM architecture versions, see Table 29.
XX represents the target architecture and its value depends on the target architecture. For example, if you specify the compiler options --cpu=4T or --cpu=ARM7TDMI then __TARGET_ARCH_4T is defined.
XX represents the target CPU. The value of XX
__RTTI__sizeof_int
-444-
__sizeof_long
__sizeof_ptr
__SOFTFP__
__STDC__
__STDC_VERSION____STRICT_ANSI____SUPPORT_SNAN__
----num
__TARGET_ARCH_ARM
__TARGET_ARCH_THUMBnum
__TARGET_ARCH_XX
-
__TARGET_CPU_XX
-
mk:@MSITStore:C:\\Keil_v5\\ARM\\HLP\\armccref.chm::/armccref_babjf...2014-6-20
Compiler Reference Guide: Predefined macrosPage 4of 6
is derived from the --cpu compiler option, or the default if none is specified. For example, if you specify the compiler option --cpu=ARM7TM then __TARGET_CPU_ARM7TM is defined and no other symbol starting with __TARGET_CPU_ is defined.
If you specify the target architecture, then __TARGET_CPU_generic is defined.
If the CPU name specified with --cpu is in lowercase, it is converted to uppercase. For example, --cpu=Cortex-R4 results in __TARGET_CPU_CORTEX_R4 being defined (rather than __TARGET_CPU_Cortex_R4). If the processor name contains hyphen (-)
characters, these are mapped to an underscore (_). For example, --cpu=ARM1136JF-S is mapped to __TARGET_CPU_ARM1136JF_S.
__TARGET_FEATURE_DOUBLEWORD__TARGET_FEATURE_DSPMUL__TARGET_FEATURE_MULTIPLY
----ARMv5T and above.
If the DSP-enhanced multiplier is available, for example ARMv5TE.
If the target architecture supports the long multiply instructions MULL and MULAL.
If the target architecture supports the
hardware divide instruction (that is, ARMv7-M or ARMv7-R).
If the target architecture supports Thumb, ARMv4T or later.
One of the following is set to indicate the FPU usage:
__TARGET_FEATURE_DIVIDE
__TARGET_FEATURE_THUMB__TARGET_FPU_xx
--
__TARGET_FPU_NONE __TARGET_FPU_VFP __TARGET_FPU_SOFTVFP
In addition, if compiling with one of the following --fpu options, the corresponding target name is set:
--fpu=softvfp+vfpv2,
__TARGET_FPU_SOFTVFP_VFPV2 --fpu=softvfp+vfpv3,
__TARGET_FPU_SOFTVFP_VFPV3
mk:@MSITStore:C:\\Keil_v5\\ARM\\HLP\\armccref.chm::/armccref_babjf...2014-6-20
Compiler Reference Guide: Predefined macrosPage 5of 6
--fpu=softvfp+vfpv3_fp16,
__TARGET_FPU_SOFTVFP_VFPV3_FP16 --fpu=softvfp+vfpv3_d16,
__TARGET_FPU_SOFTVFP_VFPV3_D16 --fpu=softvfp+vfpv3_d16_fp16,
__TARGET_FPU_SOFTVFP_VFPV3_D16_FP16 --fpu=vfpv2, __TARGET_FPU_VFPV2 --fpu=vfpv3, __TARGET_FPU_VFPV3 --fpu=vfpv3_fp16,
__TARGET_FPU_VFPV3_FP16 --fpu=vfpv3_d16,
__TARGET_FPU_VFPV3_D16 --fpu=vfpv3_d16_fp16,
__TARGET_FPU_VFPV3_D16_FP16 --fpu=vfpv4, __TARGET_FPU_VFPV4 --fpu=vfpv4_d16,
__TARGET_FPU_VFPV4_D16
See --fpu=name for more information.
__TARGET_PROFILE_R__TARGET_PROFILE_M
When you specify the --cpu=7-R option.When you specify any of the following options:
--cpu=6-M --cpu=6S-M --cpu=7-M
__thumb__
-
When the compiler is in Thumb state. That is, you have either specified the --thumb option on the command-line or #pragma thumb in your source code.
Note
The compiler might generate some ARM code even if it is compiling for Thumb. __thumb and __thumb__ become defined or undefined when using #pragma thumb or #pragma arm, but do not change in cases where Thumb functions are
generated as ARM code for other reasons
mk:@MSITStore:C:\\Keil_v5\\ARM\\HLP\\armccref.chm::/armccref_babjf...2014-6-20
Compiler Reference Guide: Predefined macrosPage 6of 6
(for example, a function specified as __irq).
__TIME___WCHAR_T
[a]
time-
Always defined.
In C++ mode, to specify that wchar_t is a keyword.
ARM recommends that if you have source code reliant on the __OPTIMISE_LEVEL macro to determine whether or not --multifile is in effect, you change to using__MULTIFILE.
Table 29 shows the possible values for __TARGET_ARCH_THUMB (see Table 28), and how these values relate to versions of the ARM architecture.
Table 29. Thumb architecture versions in relation to ARM architecture versions ARM architecture__TARGET_ARCH_ARM__TARGET_ARCH_THUMBv4v4T
v5T, v5TE, v5TEJv6, v6K, v6Zv6T2v6-M, v6S-Mv7-R
v7-M, v7E-M
44566070
01234344
Built-in function name variables.
Copyright © Keil, An ARM Company. All rights reserved.
mk:@MSITStore:C:\\Keil_v5\\ARM\\HLP\\armccref.chm::/armccref_babjf...2014-6-20
因篇幅问题不能全部显示，请点此查看更多更全内容