Preliminary Alpha support, courtesy Ioannis E. Venetis <venetis@capsl.udel.edu>.
/trunk/docs/CREDITS | 3 3 0 0 +
/trunk/samples/alphaev56-unknown-linux-gnu/crosstool.config | 282 282 0 0 +++++++++++++++++++
/trunk/config/target.in | 9 9 0 0 +
/trunk/arch/alpha/functions | 9 9 0 0 +
/trunk/arch/alpha/config.in | 58 58 0 0 ++++
5 files changed, 361 insertions(+)
1 # Target definition: architecture, optimisations, etc...
5 comment "General target options"
9 default "alpha" if ARCH_ALPHA
10 default "arm" if ARCH_ARM
11 default "ia64" if ARCH_IA64
12 default "mips" if ARCH_MIPS
13 default "powerpc" if ARCH_PPC
14 default "sh" if ARCH_SH
15 default "x86" if ARCH_x86
16 default "x86_64" if ARCH_x86_64
20 prompt "Target architecture:"
25 prompt "alpha (EXPERIMENTAL)"
26 depends on EXPERIMENTAL
31 select ARCH_SUPPORTS_BOTH_ENDIAN
32 select ARCH_DEFAULT_LE
36 prompt "ia64 (EXPERIMENTAL)"
37 depends on EXPERIMENTAL
38 select ARCH_SUPPORTS_BOTH_ENDIAN
43 select ARCH_SUPPORTS_BOTH_ENDIAN
44 select ARCH_DEFAULT_BE
52 prompt "sh (EXPERIMENTAL)"
53 depends on EXPERIMENTAL
54 select ARCH_SUPPORTS_BOTH_ENDIAN
55 select ARCH_DEFAULT_LE
67 config ARCH_SUPPORTS_BOTH_ENDIAN
71 config ARCH_DEFAULT_BE
75 config ARCH_DEFAULT_LE
82 depends on ARCH_SUPPORTS_BOTH_ENDIAN
83 default ARCH_BE if ARCH_DEFAULT_BE
84 default ARCH_LE if ARCH_DEFAULT_LE
92 prompt "Little endian"
96 # Include architecture-specific configuration
98 source config/arch/alpha/config.in
101 source config/arch/arm/config.in
104 source config/arch/ia64/config.in
107 source config/arch/mips/config.in
110 source config/arch/powerpc/config.in
113 source config/arch/sh/config.in
116 source config/arch/x86/config.in
119 source config/arch/x86_64/config.in
122 comment "Target optimisations"
126 prompt "Architecture level"
129 GCC uses this name to determine what kind of instructions it can emit
130 when generating assembly code. This option can be used in conjunction
131 with or instead of the ARCH_CPU option (above), or a (command-line)
134 This is the configuration flag --with-arch=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 "Generate code for the specific ABI"
148 Generate code for the given ABI.
150 This is the configuration flag --with-abi=XXXX, and the runtime flag
153 Pick a value from the gcc manual for your choosen gcc version and your
156 Leave blank if you don't know, or if your target architecutre does not
161 prompt "Emit assembly for CPU"
164 This specifies the name of the target processor. GCC uses this name
165 to determine what kind of instructions it can emit when generating
168 This is the configuration flag --with-cpu=XXXX, and the runtime flag
171 Pick a value from the gcc manual for your choosen gcc version and your
174 Leave blank if you don't know, or if your target architecture does not
179 prompt "Tune for CPU"
182 This option is very similar to the ARCH_CPU option (above), except
183 that instead of specifying the actual target processor type, and hence
184 restricting which instructions can be used, it specifies that GCC should
185 tune the performance of the code as if the target were of the type
186 specified in this option, but still choosing the instructions that it
187 will generate based on the cpu specified by the ARCH_CPU option
188 (above), or a (command-line) -mcpu= option.
190 This is the configuration flag --with-tune=XXXX, and the runtime flag
193 Pick a value from the gcc manual for your choosen gcc version and your
196 Leave blank if you don't know, or if your target architecture does not
201 prompt "Use specific FPU"
204 On some targets (eg. ARM), you can specify the kind of FPU to emit
207 This is the configuration flag --with-fpu=XXX, and the runtime flag
210 See below wether to actually emit FP opcodes, or to emulate them.
212 Pick a value from the gcc manual for your choosen gcc version and your
215 Leave blank if you don't know, or if your target architecture does not
220 prompt "Floating point:"
224 prompt "hardware (FPU)"
226 Emit hardware floating point opcodes.
228 If you've got a processor with a FPU, then you want that.
229 If your hardware has no FPU, you still can use HW floating point, but
230 need to compile support for FPU emulation in your kernel. Needless to
231 say that emulating the FPU is /slooowwwww/...
233 One situation you'd want HW floating point without a FPU is if you get
234 binary blobs from different vendors that are compiling this way and
235 can't (don't wan't to) change.
241 Do not emit any hardware floating point opcode.
243 If your processor has no FPU, then you most probably want this, as it
244 is faster than emulating the FPU in the kernel.
250 prompt "Target CFLAGS"
253 Used to add specific options when compiling libraries of the toolchain,
254 that will run on the target (eg. libc.so).
256 Note that the options above for ARCH, ABI, CPU, TUNE and FPU will be
257 automaticaly used. You don't need to specify them here.
259 Leave blank if you don't know better.