| /linux-3.3/scripts/ |
| D | gcc-version.sh | 3 # gcc-version [-p] gcc-command
5 # Prints the gcc version of `gcc-command' in a canonical 4-digit form
6 # such as `0295' for gcc-2.95, `0303' for gcc-3.3, etc.
9 # gcc-2.95.3, `030301' for gcc-3.3.1, etc.
21 printf "Usage:\n\t$0 <gcc-command>\n"
|
| /linux-3.3/kernel/gcov/ |
| D | gcov.h | 4 * This file is based on gcc-internal definitions. Data structures are
5 * defined to be compatible with gcc counterparts. For a better
6 * understanding, refer to gcc source: gcc/gcov-io.h.
11 * Uses gcc-internal data definitions.
20 * Profiling data types used for gcc 3.4 and above - these are defined by
21 * gcc and need to be kept as close to the original definition as possible to
43 * This data is generated by gcc during compilation and doesn't change
58 * This data is generated by gcc during compilation and doesn't change
69 * @version: gcov version magic indicating the gcc version used for compilation
78 * This data is generated by gcc during compilation and doesn't change
|
| D | gcc_3_4.c | 2 * This code provides functions to handle gcc's profiling data format
3 * introduced with gcc 3.4. Future versions of gcc may change the gcov
7 * This file is based on gcc-internal definitions. Functions and data
8 * structures are defined to be compatible with gcc counterparts.
9 * For a better understanding, refer to gcc source: gcc/gcov-io.h.
14 * Uses gcc-internal data definitions.
31 * Determine whether a counter is active. Based on gcc magic. Doesn't change
39 /* Determine number of active counters. Based on gcc magic. */
99 /* Get size of function info entry. Based on gcc magic. */
111 /* Get address of function info entry. Based on gcc magic. */
[all …]
|
| D | base.c | 7 * Uses gcc-internal data definitions.
28 * __gcov_init is called by gcc-generated constructor code for each object
39 * Printing gcc's version magic may prove useful for debugging in __gcov_init()
57 * These functions may be referenced by gcc-generated profiling code but serve
|
| /linux-3.3/include/linux/ |
| D | compiler-gcc.h | 2 #error "Please don't include <linux/compiler-gcc.h> directly, include <linux/compiler.h> instead."
6 * Common definitions for all gcc versions go here.
11 /* The "volatile" is due to gcc bugs */
15 * This macro obfuscates arithmetic on a variable address so that gcc
20 * gcc optimizers assume this is the case. In particular they
46 * or if gcc is too old:
71 * therefore they must be noinline and noclone. GCC 4.[56] currently fail to enforce
72 * this, so we must do so ourselves. See GCC PR44290.
79 * From the GCC manual:
97 #define _gcc_header(x) __gcc_header(linux/compiler-gcc##x.h)
|
| D | compiler-gcc4.h | 5 /* GCC 4.1.[01] miscompiles __weak */
8 # error Your version of gcc miscompiles the __weak directive
17 /* Mark functions as cold. gcc will assume any path leading to a call
23 Early snapshots of gcc 4.3 don't support this and we can't detect this
27 gcc also has a __attribute__((__hot__)) to move hot functions into
40 * Early snapshots of gcc 4.5 don't support this and we can't detect
|
| D | compiler.h | 48 #include <linux/compiler-gcc.h>
173 * Allow us to mark functions as 'deprecated' and have gcc emit a nice
207 * As of gcc 3.4, static functions that are not marked with attribute((used))
208 * may be elided from the assembly file. As of gcc 3.4, static data not so
209 * marked will not be elided, but this may change in a future gcc version.
212 * compiler in gcc 3.3, we must define __used to be __attribute__((used))
213 * for gcc >=3.3 instead of 3.4.
215 * In prior versions of gcc, such functions and data would be emitted, but
250 * From the GCC manual:
268 * Tell gcc if a function is cold. The compiler will assume any path
|
| /linux-3.3/arch/x86/ |
| D | Kconfig.debug | 263 bool "Allow gcc to uninline functions marked 'inline'"
265 This option determines if the kernel forces gcc to inline the functions
266 developers have marked 'inline'. Doing so takes away freedom from gcc to
267 do what it thinks is best, which is desirable for the gcc 3.x series of
268 compilers. The gcc 4.x series have a rewritten inlining algorithm and
270 this algorithm is so good that allowing gcc 4.x and above to make the
272 is there to test gcc for this.
285 the copy operation, by having gcc prove that the argument is
288 If unsure, or if you run an older (pre 4.4) gcc, say N.
|
| D | Makefile.um | 24 # prevent gcc from keeping the stack 16 byte aligned. Taken from i386.
31 # Disable unit-at-a-time mode on pre-gcc-4.0 compilers, it makes gcc use
32 # a lot more stack due to the lack of sharing of stacklots. Also, gcc
|
| D | Kconfig.cpu | 155 flags to GCC.
163 flags to GCC.
170 optimization flags to GCC.
177 like a 586 with TSC, and sets some GCC optimization flags (like a
190 Select this for an IDT Winchip C6 chip. Linux and GCC
198 Select this for an IDT Winchip-2, 2A or 3. Linux and GCC
228 Select this for a Cyrix III or C3 chip. Presently Linux and GCC
230 it lacks the cmov extension which gcc assumes is present when
241 of SSE and tells gcc to treat the CPU as a 686.
249 shift and tells gcc to treat the CPU as a 686.
[all …]
|
| D | Makefile | 30 # prevent gcc from keeping the stack 16 byte aligned
33 # Disable unit-at-a-time mode on pre-gcc-4.0 compilers, it makes gcc use
76 cc_has_sp := $(srctree)/scripts/gcc-x86_$(BITS)-has-stack-protector.sh
110 # Workaround for a gcc prelease that unfortunately was shipped in a suse release
114 # prevent gcc from generating any FP code by mistake
|
| /linux-3.3/arch/x86/boot/ |
| D | code16gcc.h | 5 * Note: this asm() needs to be emitted before gcc emits any code.
6 * Depending on gcc version, this requires -fno-unit-at-a-time or
9 * Hopefully gcc will eventually have a real -m16 option so we can
|
| /linux-3.3/arch/x86/include/asm/ |
| D | page.h | 39 This seems to be the official gcc blessed way to do such arithmetic. */
41 * We need __phys_reloc_hide() here because gcc may assume that there is no
43 * Newer versions of gcc provide -fno-strict-overflow switch to handle this
44 * case properly. Once all supported versions of gcc understand it, we can
|
| /linux-3.3/Documentation/ia64/ |
| D | README | 16 Compiling and running this kernel requires an IA-64 compliant GCC
18 IA-64 compliant GCC compiler.
30 compliant GCC compiler.
|
| /linux-3.3/arch/powerpc/ |
| D | Makefile | 20 CROSS32CC := $(CROSS32_COMPILE)gcc
117 # revert to pre-gcc-4.4 behaviour of .eh_frame
128 # Work around a gcc code-gen bug with -fno-omit-frame-pointer.
238 # gcc-3.4 and binutils-2.14 are a fatal combination.
244 echo 'correctly with gcc-3.4 and your version of binutils.'; \
245 echo '*** Please upgrade your binutils or downgrade your gcc'; \
251 echo -n '*** GCC-4.2.0 cannot compile the 64-bit powerpc ' ; \
253 echo -n '*** Please use a different GCC version or ' ; \
|
| /linux-3.3/arch/arm/include/asm/ |
| D | div64.h | 52 * gcc versions earlier than 4.0 are simply too problematic for the
53 * optimized implementation below. First there is gcc PR 15089 that
56 * generated code, and those gcc versions are not able to do constant
69 * for ARMv4 or higher (we need umull/umlal) and if the gcc version is
71 * (It is unfortunate that gcc doesn't perform all this internally.)
82 /* gcc does the right thing with this code. */ \
201 /* only, and gcc is good at that. */ \
|
| /linux-3.3/arch/cris/arch-v32/lib/ |
| D | usercopy.c | 14 satisfactory results for "gcc version 3.2.1 Axis release R53/1.53-v32".
36 FIXME: Comment for old gcc version. Check. in __copy_user()
37 If gcc was alright, it really would need no temporaries, and no in __copy_user()
79 ;; The GCC manual explicitly says TRT will happen. \n\ in __copy_user()
170 FIXME: Comment for old gcc version. Check. in __copy_user_zeroing()
171 If gcc was alright, it really would need no temporaries, and no in __copy_user_zeroing()
334 FIXME: Comment for old gcc version. Check. in __do_clear_user()
335 If gcc was alright, it really would need no temporaries, and no in __do_clear_user()
386 ;; on the stack. Don't mention them to gcc, it will only be \n\ in __do_clear_user()
|
| D | memset.c | 30 result is somewhat depending on gcc generating what we expect rather
59 /* This is fragile performancewise at best. Check with newer GCC in memset()
102 ;; GCC does promise correct register allocations, but let's \n\ in memset()
105 .error \"GCC reg alloc bug: %0-%1-%4 != $r13-$r12-$r11\" \n\ in memset()
109 ;; on the stack. Don't mention them to gcc, it will only be \n\ in memset()
|
| /linux-3.3/arch/unicore32/kernel/ |
| D | asm-offsets.c | 26 * GCC 3.0, 3.1: general bad code generation.
27 * GCC 3.2.0: incorrect function argument offset calculation.
28 * GCC 3.2.x: miscompiles NEW_AUX_ENT in fs/binfmt_elf.c
29 * (http://gcc.gnu.org/PR8896) and incorrect structure
|
| /linux-3.3/arch/h8300/include/asm/ |
| D | uaccess.h | 78 * Tell gcc we read from memory instead of writing: this is because
79 * we do not write to any memory gcc knows about, so there are no
86 * Tell gcc we read from memory instead of writing: this is because
87 * we do not write to any memory gcc knows about, so there are no
|
| /linux-3.3/include/xen/ |
| D | xencomm.h | 49 * gcc bug workaround:
50 * http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16660
51 * gcc doesn't handle properly stack variable with
|
| /linux-3.3/arch/arm/kernel/ |
| D | asm-offsets.c | 33 * GCC 3.0, 3.1: general bad code generation.
34 * GCC 3.2.0: incorrect function argument offset calculation.
35 * GCC 3.2.x: miscompiles NEW_AUX_ENT in fs/binfmt_elf.c
36 * (http://gcc.gnu.org/PR8896) and incorrect structure
|
| /linux-3.3/arch/parisc/ |
| D | Kconfig.debug | 24 the copy operation, by having gcc prove that the argument is
27 If unsure, or if you run an older (pre 4.4) gcc, say N.
|
| /linux-3.3/arch/s390/ |
| D | Kconfig.debug | 29 the copy operation, by having gcc prove that the argument is
32 If unsure, or if you run an older (pre 4.4) gcc, say N.
|
| /linux-3.3/arch/cris/arch-v10/lib/ |
| D | memset.c | 30 result is somewhat depending on gcc generating what we expect rather
59 /* This is fragile performancewise at best. Check with newer GCC in memset()
102 ;; GCC does promise correct register allocations, but let's \n\ in memset()
105 .error \"GCC reg alloc bug: %0-%1-%4 != $r13-$r12-$r11\" \n\ in memset()
109 ;; on the stack. Don't mention them to gcc, it will only be \n\ in memset()
|