Merge from branches/ia64@476 : add ia64 preliminary support.
1 # Target definition: architecture, optimisations, etc...
5 comment "General target options"
9 default "arm" if ARCH_ARM
10 default "ia64" if ARCH_IA64
11 default "mips" if ARCH_MIPS
12 default "x86" if ARCH_x86
13 default "x86_64" if ARCH_x86_64
17 prompt "Target architecture:"
23 select ARCH_SUPPORTS_BOTH_ENDIAN
24 select ARCH_DEFAULT_LE
28 prompt "ia64 (EXPERIMENTAL)"
29 depends on EXPERIMENTAL
30 select ARCH_SUPPORTS_BOTH_ENDIAN
35 select ARCH_SUPPORTS_BOTH_ENDIAN
36 select ARCH_DEFAULT_BE
48 config ARCH_SUPPORTS_BOTH_ENDIAN
52 config ARCH_DEFAULT_BE
56 config ARCH_DEFAULT_LE
63 depends on ARCH_SUPPORTS_BOTH_ENDIAN
64 default ARCH_BE if ARCH_DEFAULT_BE
65 default ARCH_LE if ARCH_DEFAULT_LE
73 prompt "Little endian"
77 comment "Target optimisations"
81 prompt "Achitecture level"
84 GCC uses this name to determine what kind of instructions it can emit
85 when generating assembly code. This option can be used in conjunction
86 with or instead of the ARCH_CPU option (above), or a (command-line)
89 This is the configuration flag --with-arch=XXXX, and the runtime flag
92 Pick a value from the gcc manual for your choosen gcc version and your
95 Leave blank if you don't know, or if your target architecture does not
100 prompt "Generate code for the specific ABI"
103 Generate code for the given ABI.
105 This is the configuration flag --with-abi=XXXX, and the runtime flag
108 Pick a value from the gcc manual for your choosen gcc version and your
111 Leave blank if you don't know, or if your target architecutre does not
116 prompt "Emit assembly for CPU"
119 This specifies the name of the target processor. GCC uses this name
120 to determine what kind of instructions it can emit when generating
123 This is the configuration flag --with-cpu=XXXX, and the runtime flag
126 Pick a value from the gcc manual for your choosen gcc version and your
129 Leave blank if you don't know, or if your target architecture does not
134 prompt "Tune for CPU"
137 This option is very similar to the ARCH_CPU option (above), except
138 that instead of specifying the actual target processor type, and hence
139 restricting which instructions can be used, it specifies that GCC should
140 tune the performance of the code as if the target were of the type
141 specified in this option, but still choosing the instructions that it
142 will generate based on the cpu specified by the ARCH_CPU option
143 (above), or a (command-line) -mcpu= option.
145 This is the configuration flag --with-tune=XXXX, and the runtime flag
148 Pick a value from the gcc manual for your choosen gcc version and your
151 Leave blank if you don't know, or if your target architecture does not
156 prompt "Use specific FPU"
159 On some targets (eg. ARM), you can specify the kind of FPU to emit
162 This is the configuration flag --with-fpu=XXX, and the runtime flag
165 See below wether to actually emit FP opcodes, or to emulate them.
167 Pick a value from the gcc manual for your choosen gcc version and your
170 Leave blank if you don't know, or if your target architecture does not
175 prompt "Floating point:"
179 prompt "hardware (FPU)"
181 Emit hardware floating point opcodes.
183 If you've got a processor with a FPU, then you want that.
184 If your hardware has no FPU, you still can use HW floating point, but
185 need to compile support for FPU emulation in your kernel. Needless to
186 say that emulating the FPU is /slooowwwww/...
188 One situation you'd want HW floating point without a FPU is if you get
189 binary blobs from different vendors that are compiling this way and
190 can't (don't wan't to) change.
196 Do not emit any hardware floating point opcode.
198 If your processor has no FPU, then you most probably want this, as it
199 is faster than emulating the FPU in the kernel.
205 prompt "Target CFLAGS"
208 Used to add specific options when compiling libraries of the toolchain,
209 that will run on the target (eg. libc.so).
211 Note that the options above for CPU, tune, arch and FPU will be
212 automaticaly used. You don't need to specify them here.
214 Leave blank if you don't know better.