Introduce the notion of a 'sample comment'.
- presence of the sample's reported.by file is now mandatory.
- when saving a sample, reporter name & URL are queried, to avoid operator forget about creating the reported.by file.
- when saving a sample, one can store a few-liner comment.
- when recalling a sample, the reporter name, URL and comment (if present) are printed.
- update the powerpc-e500v2-linux-gnuspe sample to include Nate's comment (from his original mail).
- update all samples that were missing the reported.by file.
/trunk/scripts/saveSample.sh | 46 35 11 0 ++++++++++++++++++------
/trunk/scripts/showSamples.sh | 12 6 6 0 +++---
/trunk/samples/powerpc-e500v2-linux-gnuspe/reported.by | 15 15 0 0 ++++++++
/trunk/samples/samples.mk | 22 17 5 0 +++++++++--
4 files changed, 73 insertions(+), 22 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
29 comment "General target options"
31 source config.gen/arch.in
33 config ARCH_SUPPORTS_BOTH_ENDIAN
37 config ARCH_DEFAULT_BE
41 config ARCH_DEFAULT_LE
48 depends on ARCH_SUPPORTS_BOTH_ENDIAN
49 default ARCH_BE if ARCH_DEFAULT_BE
50 default ARCH_LE if ARCH_DEFAULT_LE
58 prompt "Little endian"
62 comment "Target optimisations"
64 config ARCH_SUPPORT_ARCH
68 config ARCH_SUPPORT_ABI
72 config ARCH_SUPPORT_CPU
76 config ARCH_SUPPORT_TUNE
80 config ARCH_SUPPORT_FPU
86 prompt "Architecture level"
87 depends on ARCH_SUPPORT_ARCH
90 GCC uses this name to determine what kind of instructions it can emit
91 when generating assembly code. This option can be used in conjunction
92 with or instead of the ARCH_CPU option (above), or a (command-line)
95 This is the configuration flag --with-arch=XXXX, and the runtime flag
98 Pick a value from the gcc manual for your choosen gcc version and your
101 Leave blank if you don't know, or if your target architecture does not
106 prompt "Generate code for the specific ABI"
107 depends on ARCH_SUPPORT_ABI
110 Generate code for the given ABI.
112 This is the configuration flag --with-abi=XXXX, and the runtime flag
115 Pick a value from the gcc manual for your choosen gcc version and your
118 Leave blank if you don't know, or if your target architecutre does not
123 prompt "Emit assembly for CPU"
124 depends on ARCH_SUPPORT_CPU
127 This specifies the name of the target processor. GCC uses this name
128 to determine what kind of instructions it can emit when generating
131 This is the configuration flag --with-cpu=XXXX, and the runtime flag
134 Pick a value from the gcc manual for your choosen gcc version and your
137 Leave blank if you don't know, or if your target architecture does not
142 prompt "Tune for CPU"
143 depends on ARCH_SUPPORT_TUNE
146 This option is very similar to the ARCH_CPU option (above), except
147 that instead of specifying the actual target processor type, and hence
148 restricting which instructions can be used, it specifies that GCC should
149 tune the performance of the code as if the target were of the type
150 specified in this option, but still choosing the instructions that it
151 will generate based on the cpu specified by the ARCH_CPU option
152 (above), or a (command-line) -mcpu= option.
154 This is the configuration flag --with-tune=XXXX, and the runtime flag
157 Pick a value from the gcc manual for your choosen gcc version and your
160 Leave blank if you don't know, or if your target architecture does not
165 prompt "Use specific FPU"
166 depends on ARCH_SUPPORT_FPU
169 On some targets (eg. ARM), you can specify the kind of FPU to emit
172 This is the configuration flag --with-fpu=XXX, and the runtime flag
175 See below wether to actually emit FP opcodes, or to emulate them.
177 Pick a value from the gcc manual for your choosen gcc version and your
180 Leave blank if you don't know, or if your target architecture does not
185 prompt "Floating point:"
189 prompt "hardware (FPU)"
191 Emit hardware floating point opcodes.
193 If you've got a processor with a FPU, then you want that.
194 If your hardware has no FPU, you still can use HW floating point, but
195 need to compile support for FPU emulation in your kernel. Needless to
196 say that emulating the FPU is /slooowwwww/...
198 One situation you'd want HW floating point without a FPU is if you get
199 binary blobs from different vendors that are compiling this way and
200 can't (don't wan't to) change.
206 Do not emit any hardware floating point opcode.
208 If your processor has no FPU, then you most probably want this, as it
209 is faster than emulating the FPU in the kernel.
215 prompt "Target CFLAGS"
218 Used to add specific options when compiling libraries of the toolchain,
219 that will run on the target (eg. libc.so).
221 Note that the options above for ARCH, ABI, CPU, TUNE and FPU will be
222 automaticaly used. You don't need to specify them here.
224 Leave blank if you don't know better.
226 config TARGET_LDFLAGS
228 prompt "Target LDFLAGS"
231 Used to add specific options when linking libraries of the toolchain,
232 that will run on your target.
234 Leave blank if you don't know better.