Only present each of arch, abi, cpu tune and fpu optimisations for those targets supporting them.
/trunk/config/target.in | 30 30 0 0 ++++++++++++++++++++++++++++++
/trunk/arch/arm/config.in | 5 5 0 0 +++++
/trunk/arch/powerpc/config.in | 3 3 0 0 +++
/trunk/arch/alpha/config.in | 2 2 0 0 ++
/trunk/arch/x86/config.in | 3 3 0 0 +++
/trunk/arch/mips/config.in | 3 3 0 0 +++
/trunk/arch/x86_64/config.in | 3 3 0 0 +++
7 files changed, 49 insertions(+)
1 # Target definition: architecture, optimisations, etc...
8 # Pre-declare target optimisation variables
9 config ARCH_SUPPORT_ARCH
11 config ARCH_SUPPORT_ABI
13 config ARCH_SUPPORT_CPU
15 config ARCH_SUPPORT_TUNE
17 config ARCH_SUPPORT_FPU
19 config ARCH_SUPPORTS_BOTH_ENDIAN
20 config ARCH_DEFAULT_BE
21 config ARCH_DEFAULT_LE
26 comment "General target options"
30 prompt "Target architecture:"
32 source config.gen/arch.in
36 config ARCH_SUPPORTS_BOTH_ENDIAN
40 config ARCH_DEFAULT_BE
44 config ARCH_DEFAULT_LE
51 depends on ARCH_SUPPORTS_BOTH_ENDIAN
52 default ARCH_BE if ARCH_DEFAULT_BE
53 default ARCH_LE if ARCH_DEFAULT_LE
61 prompt "Little endian"
65 comment "Target optimisations"
67 config ARCH_SUPPORT_ARCH
71 config ARCH_SUPPORT_ABI
75 config ARCH_SUPPORT_CPU
79 config ARCH_SUPPORT_TUNE
83 config ARCH_SUPPORT_FPU
89 prompt "Architecture level"
90 depends on ARCH_SUPPORT_ARCH
93 GCC uses this name to determine what kind of instructions it can emit
94 when generating assembly code. This option can be used in conjunction
95 with or instead of the ARCH_CPU option (above), or a (command-line)
98 This is the configuration flag --with-arch=XXXX, and the runtime flag
101 Pick a value from the gcc manual for your choosen gcc version and your
104 Leave blank if you don't know, or if your target architecture does not
109 prompt "Generate code for the specific ABI"
110 depends on ARCH_SUPPORT_ABI
113 Generate code for the given ABI.
115 This is the configuration flag --with-abi=XXXX, and the runtime flag
118 Pick a value from the gcc manual for your choosen gcc version and your
121 Leave blank if you don't know, or if your target architecutre does not
126 prompt "Emit assembly for CPU"
127 depends on ARCH_SUPPORT_CPU
130 This specifies the name of the target processor. GCC uses this name
131 to determine what kind of instructions it can emit when generating
134 This is the configuration flag --with-cpu=XXXX, and the runtime flag
137 Pick a value from the gcc manual for your choosen gcc version and your
140 Leave blank if you don't know, or if your target architecture does not
145 prompt "Tune for CPU"
146 depends on ARCH_SUPPORT_TUNE
149 This option is very similar to the ARCH_CPU option (above), except
150 that instead of specifying the actual target processor type, and hence
151 restricting which instructions can be used, it specifies that GCC should
152 tune the performance of the code as if the target were of the type
153 specified in this option, but still choosing the instructions that it
154 will generate based on the cpu specified by the ARCH_CPU option
155 (above), or a (command-line) -mcpu= option.
157 This is the configuration flag --with-tune=XXXX, and the runtime flag
160 Pick a value from the gcc manual for your choosen gcc version and your
163 Leave blank if you don't know, or if your target architecture does not
168 prompt "Use specific FPU"
169 depends on ARCH_SUPPORT_FPU
172 On some targets (eg. ARM), you can specify the kind of FPU to emit
175 This is the configuration flag --with-fpu=XXX, and the runtime flag
178 See below wether to actually emit FP opcodes, or to emulate them.
180 Pick a value from the gcc manual for your choosen gcc version and your
183 Leave blank if you don't know, or if your target architecture does not
188 prompt "Floating point:"
192 prompt "hardware (FPU)"
194 Emit hardware floating point opcodes.
196 If you've got a processor with a FPU, then you want that.
197 If your hardware has no FPU, you still can use HW floating point, but
198 need to compile support for FPU emulation in your kernel. Needless to
199 say that emulating the FPU is /slooowwwww/...
201 One situation you'd want HW floating point without a FPU is if you get
202 binary blobs from different vendors that are compiling this way and
203 can't (don't wan't to) change.
209 Do not emit any hardware floating point opcode.
211 If your processor has no FPU, then you most probably want this, as it
212 is faster than emulating the FPU in the kernel.
218 prompt "Target CFLAGS"
221 Used to add specific options when compiling libraries of the toolchain,
222 that will run on the target (eg. libc.so).
224 Note that the options above for ARCH, ABI, CPU, TUNE and FPU will be
225 automaticaly used. You don't need to specify them here.
227 Leave blank if you don't know better.