Re-instatethe fortran forntend for this sample.
/trunk/samples/armeb-unknown-linux-gnu/crosstool.config | 4 2 2 0 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
1 # Target definition: architecture, optimisations, etc...
8 # Pre-declare target optimisation variables
9 config ARCH_SUPPORT_ARCH
10 config ARCH_SUPPORT_ABI
11 config ARCH_SUPPORT_CPU
12 config ARCH_SUPPORT_TUNE
13 config ARCH_SUPPORT_FPU
14 config ARCH_SUPPORTS_BOTH_ENDIAN
15 config ARCH_DEFAULT_BE
16 config ARCH_DEFAULT_LE
28 comment "General target options"
32 prompt "Target architecture:"
34 source config.gen/arch.in
38 config ARCH_SUPPORTS_BOTH_ENDIAN
42 config ARCH_DEFAULT_BE
46 config ARCH_DEFAULT_LE
53 depends on ARCH_SUPPORTS_BOTH_ENDIAN
54 default ARCH_BE if ARCH_DEFAULT_BE
55 default ARCH_LE if ARCH_DEFAULT_LE
63 prompt "Little endian"
67 comment "Target optimisations"
69 config ARCH_SUPPORT_ARCH
73 config ARCH_SUPPORT_ABI
77 config ARCH_SUPPORT_CPU
81 config ARCH_SUPPORT_TUNE
85 config ARCH_SUPPORT_FPU
91 prompt "Architecture level"
92 depends on ARCH_SUPPORT_ARCH
95 GCC uses this name to determine what kind of instructions it can emit
96 when generating assembly code. This option can be used in conjunction
97 with or instead of the ARCH_CPU option (above), or a (command-line)
100 This is the configuration flag --with-arch=XXXX, and the runtime flag
103 Pick a value from the gcc manual for your choosen gcc version and your
106 Leave blank if you don't know, or if your target architecture does not
111 prompt "Generate code for the specific ABI"
112 depends on ARCH_SUPPORT_ABI
115 Generate code for the given ABI.
117 This is the configuration flag --with-abi=XXXX, and the runtime flag
120 Pick a value from the gcc manual for your choosen gcc version and your
123 Leave blank if you don't know, or if your target architecutre does not
128 prompt "Emit assembly for CPU"
129 depends on ARCH_SUPPORT_CPU
132 This specifies the name of the target processor. GCC uses this name
133 to determine what kind of instructions it can emit when generating
136 This is the configuration flag --with-cpu=XXXX, and the runtime flag
139 Pick a value from the gcc manual for your choosen gcc version and your
142 Leave blank if you don't know, or if your target architecture does not
147 prompt "Tune for CPU"
148 depends on ARCH_SUPPORT_TUNE
151 This option is very similar to the ARCH_CPU option (above), except
152 that instead of specifying the actual target processor type, and hence
153 restricting which instructions can be used, it specifies that GCC should
154 tune the performance of the code as if the target were of the type
155 specified in this option, but still choosing the instructions that it
156 will generate based on the cpu specified by the ARCH_CPU option
157 (above), or a (command-line) -mcpu= option.
159 This is the configuration flag --with-tune=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 "Use specific FPU"
171 depends on ARCH_SUPPORT_FPU
174 On some targets (eg. ARM), you can specify the kind of FPU to emit
177 This is the configuration flag --with-fpu=XXX, and the runtime flag
180 See below wether to actually emit FP opcodes, or to emulate them.
182 Pick a value from the gcc manual for your choosen gcc version and your
185 Leave blank if you don't know, or if your target architecture does not
190 prompt "Floating point:"
194 prompt "hardware (FPU)"
196 Emit hardware floating point opcodes.
198 If you've got a processor with a FPU, then you want that.
199 If your hardware has no FPU, you still can use HW floating point, but
200 need to compile support for FPU emulation in your kernel. Needless to
201 say that emulating the FPU is /slooowwwww/...
203 One situation you'd want HW floating point without a FPU is if you get
204 binary blobs from different vendors that are compiling this way and
205 can't (don't wan't to) change.
211 Do not emit any hardware floating point opcode.
213 If your processor has no FPU, then you most probably want this, as it
214 is faster than emulating the FPU in the kernel.
220 prompt "Target CFLAGS"
223 Used to add specific options when compiling libraries of the toolchain,
224 that will run on the target (eg. libc.so).
226 Note that the options above for ARCH, ABI, CPU, TUNE and FPU will be
227 automaticaly used. You don't need to specify them here.
229 Leave blank if you don't know better.