Lines Matching full:tune

21 DEFAULTTUNE - This specifies the tune to use for a particular build.
22 Each tune should specify a reasonable default, which can be overriden by
23 a machine or multilib configuration.  The specified tune must be listed
34 TUNE_FEATURES - This is automatically defined as TUNE_FEATURES:tune-<tune>.
35 See TUNE_FEATURES:tune-<tune> for more information.
37 TUNE_FEATURES:tune-<tune> - Specify the features used to describe a
38 specific tune.  This is a list of features that a tune support, each
39 feature must be in the TUNEVALID list.  Note: the tune and a given
47 ABIEXTENSION = "eabi" in the arm case, or appended to in specific tune
69 PACKAGE_EXTRA_ARCHS:tune-<tune>.  If an architecture deviates from the
72 PACKAGE_EXTRA_ARCHS:tune-<tune> - List all of the package architectures
73 that are compatible with this specific tune.  The package arch of this
74 tune must be in the list.
76 TARGET_FPU - The FPU setting for a given tune, hard (generate floating
82 BASE_LIB:tune-<tune> - The "/lib" location for a specific ABI.  This is
89 The tune infrastructure is designed to be hierarchical. When writing a
90 new tune file for a "fast-forward" CPU architecture (one that supports
92 previous generation tune file and specify PACKAGE_EXTRA_ARCHS using the
93 previous generation's override and appending the new tune. Note that
94 only one previous tune file should be included to avoid mutiple includes
99 included in the base i586 tune file. The core2 tune builds