PowerPC support by Daniel Dittmann.
/trunk/docs/CREDITS | 3 3 0 0 +++
/trunk/config/target.in | 8 8 0 0 ++++++++
/trunk/arch/powerpc/functions | 9 9 0 0 +++++++++
/trunk/arch/powerpc/config.in | 1 1 0 0 +
4 files changed, 21 insertions(+)
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 "powerpc" if ARCH_PPC
13 default "sh" if ARCH_SH
14 default "x86" if ARCH_x86
15 default "x86_64" if ARCH_x86_64
19 prompt "Target architecture:"
25 select ARCH_SUPPORTS_BOTH_ENDIAN
26 select ARCH_DEFAULT_LE
30 prompt "ia64 (EXPERIMENTAL)"
31 depends on EXPERIMENTAL
32 select ARCH_SUPPORTS_BOTH_ENDIAN
37 select ARCH_SUPPORTS_BOTH_ENDIAN
38 select ARCH_DEFAULT_BE
46 prompt "sh (EXPERIMENTAL)"
47 depends on EXPERIMENTAL
48 select ARCH_SUPPORTS_BOTH_ENDIAN
49 select ARCH_DEFAULT_LE
61 config ARCH_SUPPORTS_BOTH_ENDIAN
65 config ARCH_DEFAULT_BE
69 config ARCH_DEFAULT_LE
76 depends on ARCH_SUPPORTS_BOTH_ENDIAN
77 default ARCH_BE if ARCH_DEFAULT_BE
78 default ARCH_LE if ARCH_DEFAULT_LE
86 prompt "Little endian"
90 # Include architecture-specific configuration
92 source config/arch/arm/config.in
95 source config/arch/ia64/config.in
98 source config/arch/mips/config.in
101 source config/arch/powerpc/config.in
104 source config/arch/sh/config.in
107 source config/arch/x86/config.in
110 source config/arch/x86_64/config.in
113 comment "Target optimisations"
117 prompt "Architecture level"
120 GCC uses this name to determine what kind of instructions it can emit
121 when generating assembly code. This option can be used in conjunction
122 with or instead of the ARCH_CPU option (above), or a (command-line)
125 This is the configuration flag --with-arch=XXXX, and the runtime flag
128 Pick a value from the gcc manual for your choosen gcc version and your
131 Leave blank if you don't know, or if your target architecture does not
136 prompt "Generate code for the specific ABI"
139 Generate code for the given ABI.
141 This is the configuration flag --with-abi=XXXX, and the runtime flag
144 Pick a value from the gcc manual for your choosen gcc version and your
147 Leave blank if you don't know, or if your target architecutre does not
152 prompt "Emit assembly for CPU"
155 This specifies the name of the target processor. GCC uses this name
156 to determine what kind of instructions it can emit when generating
159 This is the configuration flag --with-cpu=XXXX, and the runtime flag
162 Pick a value from the gcc manual for your choosen gcc version and your
165 Leave blank if you don't know, or if your target architecture does not
170 prompt "Tune for CPU"
173 This option is very similar to the ARCH_CPU option (above), except
174 that instead of specifying the actual target processor type, and hence
175 restricting which instructions can be used, it specifies that GCC should
176 tune the performance of the code as if the target were of the type
177 specified in this option, but still choosing the instructions that it
178 will generate based on the cpu specified by the ARCH_CPU option
179 (above), or a (command-line) -mcpu= option.
181 This is the configuration flag --with-tune=XXXX, and the runtime flag
184 Pick a value from the gcc manual for your choosen gcc version and your
187 Leave blank if you don't know, or if your target architecture does not
192 prompt "Use specific FPU"
195 On some targets (eg. ARM), you can specify the kind of FPU to emit
198 This is the configuration flag --with-fpu=XXX, and the runtime flag
201 See below wether to actually emit FP opcodes, or to emulate them.
203 Pick a value from the gcc manual for your choosen gcc version and your
206 Leave blank if you don't know, or if your target architecture does not
211 prompt "Floating point:"
215 prompt "hardware (FPU)"
217 Emit hardware floating point opcodes.
219 If you've got a processor with a FPU, then you want that.
220 If your hardware has no FPU, you still can use HW floating point, but
221 need to compile support for FPU emulation in your kernel. Needless to
222 say that emulating the FPU is /slooowwwww/...
224 One situation you'd want HW floating point without a FPU is if you get
225 binary blobs from different vendors that are compiling this way and
226 can't (don't wan't to) change.
232 Do not emit any hardware floating point opcode.
234 If your processor has no FPU, then you most probably want this, as it
235 is faster than emulating the FPU in the kernel.
241 prompt "Target CFLAGS"
244 Used to add specific options when compiling libraries of the toolchain,
245 that will run on the target (eg. libc.so).
247 Note that the options above for CPU, tune, arch and FPU will be
248 automaticaly used. You don't need to specify them here.
250 Leave blank if you don't know better.