ARM defaults to LE, MIPS to BE. Reflect this in the target configuration options.
1 # Target definition: architecture, optimisations, etc...
5 comment "General target options"
9 default "arm" if ARCH_ARM
10 default "mips" if ARCH_MIPS
11 default "x86" if ARCH_x86
12 default "x86_64" if ARCH_x86_64
16 prompt "Target architecture:"
22 select ARCH_SUPPORTS_BOTH_ENDIAN
23 select ARCH_DEFAULT_LE
28 select ARCH_SUPPORTS_BOTH_ENDIAN
29 select ARCH_DEFAULT_BE
41 config ARCH_SUPPORTS_BOTH_ENDIAN
45 config ARCH_DEFAULT_BE
49 config ARCH_DEFAULT_LE
56 depends on ARCH_SUPPORTS_BOTH_ENDIAN
57 default ARCH_BE if ARCH_DEFAULT_BE
58 default ARCH_LE if ARCH_DEFAULT_LE
66 prompt "Little endian"
70 comment "Target optimisations"
74 prompt "Achitecture level"
77 GCC uses this name to determine what kind of instructions it can emit
78 when generating assembly code. This option can be used in conjunction
79 with or instead of the ARCH_CPU option (above), or a (command-line)
82 This is the configuration flag --with-arch=XXXX, and the runtime flag
85 Pick a value from the gcc manual for your choosen gcc version and your
88 Leave blank if you don't know, or if your target architecture does not
93 prompt "Generate code for the specific ABI"
96 Generate code for the given ABI.
98 This is the configuration flag --with-abi=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 architecutre does not
109 prompt "Emit assembly for CPU"
112 This specifies the name of the target processor. GCC uses this name
113 to determine what kind of instructions it can emit when generating
116 This is the configuration flag --with-cpu=XXXX, and the runtime flag
119 Pick a value from the gcc manual for your choosen gcc version and your
122 Leave blank if you don't know, or if your target architecture does not
127 prompt "Tune for CPU"
130 This option is very similar to the ARCH_CPU option (above), except
131 that instead of specifying the actual target processor type, and hence
132 restricting which instructions can be used, it specifies that GCC should
133 tune the performance of the code as if the target were of the type
134 specified in this option, but still choosing the instructions that it
135 will generate based on the cpu specified by the ARCH_CPU option
136 (above), or a (command-line) -mcpu= option.
138 This is the configuration flag --with-tune=XXXX, and the runtime flag
141 Pick a value from the gcc manual for your choosen gcc version and your
144 Leave blank if you don't know, or if your target architecture does not
149 prompt "Use specific FPU"
152 On some targets (eg. ARM), you can specify the kind of FPU to emit
155 This is the configuration flag --with-fpu=XXX, and the runtime flag
158 See below wether to actually emit FP opcodes, or to emulate them.
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 "Floating point:"
172 prompt "hardware (FPU)"
174 Emit hardware floating point opcodes.
176 If you've got a processor with a FPU, then you want that.
177 If your hardware has no FPU, you still can use HW floating point, but
178 need to compile support for FPU emulation in your kernel. Needless to
179 say that emulating the FPU is /slooowwwww/...
181 One situation you'd want HW floating point without a FPU is if you get
182 binary blobs from different vendors that are compiling this way and
183 can't (don't wan't to) change.
189 Do not emit any hardware floating point opcode.
191 If your processor has no FPU, then you most probably want this, as it
192 is faster than emulating the FPU in the kernel.
198 prompt "Target CFLAGS"
201 Used to add specific options when compiling libraries of the toolchain,
202 that will run on the target (eg. libc.so).
204 Note that the options above for CPU, tune, arch and FPU will be
205 automaticaly used. You don't need to specify them here.
207 Leave blank if you don't know better.