12012/03/30 - Mark Hatle <mark.hatle@windriver.com> 2 - Initial Revision 3 4The ARM architecture definitions are split among a number of files. 5The primary definitions for the variables are handled by the core 6arch-arm.inc file. 7 8TUNE_ARCH is set to either "arm" or "armeb" depending on the value 9of the existence of the "bigendian" feature in a given tune. 10 11A small set of ARM specific variables have been defined to allow 12TUNE_PKGARCH to be automatically defined. Optimized tunings must NOT 13change the definiton of TUNE_PKGARCH. TUNE_PKGACH:tune-<tune> will be 14ignored. The format of the package arch is enforced by the TUNE_PKGARCH 15default. The format must be of the form: 16<armversion>[t][e][hf][b][-vfp][-neon] 17 18TUNE_PKGARCH is defined as: 19${ARMPKGARCH}${ARMPKGSFX_THUMB}${ARMPKGSFX_DSP}${ARMPKGSFX_EABI}${ARMPKGSFX_ENDIAN}${ARMPKGSFX_FPU} 20 21ARMPKGARCH - This is the core package arch component specified by each 22tuning. This is the primary identifier of a tuning. Usual values are: 23arm, armv4, armv5, armv6, armv7a, etc. 24 25ARMPKGSFX_THUMB - This is the thumb specific suffix. Curently it is 26defined in feature-arm-thumb.inc. 27 28ARMPKGSFX_DSP - This is the DSP specific suffix. Currently this is set 29to 'e' when on armv5 and the dsp feature is enabled. 30 31ARMPKGSFX_EABI - This is the eabi specific suffix. There are currently 32two defined ABIs specificed, standard EABI and Hard Float (VFP) EABI. 33When the callconvention-hard is enabled, "hf" is specified, otherwise it 34is blank. 35 36ARMPKGSFX_ENDIAN - This is the endian specific suffix. It is defined in 37the core arch-arm.inc file. 38 39ARMPKGSFX_FPU - This is the FPU specific suffix. The suffix indicates 40specific FPU optimizations. 'vfp' and 'neon' are both defined. 41