compiler (reference) in projects: Linux-v5.10

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched refs:compiler (Results 1 – 25 of 139) sorted by relevance

12 3 4 5 6

/Linux-v5.10/scripts/
D	clang-version.sh	`9 compiler="$*" 11 if ! ( $compiler --version \| grep -q clang) ; then 16 MAJOR=$(echo __clang_major__ \| $compiler -E -x c - \| tail -n 1) 17 MINOR=$(echo __clang_minor__ \| $compiler -E -x c - \| tail -n 1) 18 PATCHLEVEL=$(echo __clang_patchlevel__ \| $compiler -E -x c - \| tail -n 1)`
D	gcc-version.sh	`9 compiler="$*" 17 MAJOR=$(echo __GNUC__ \| $compiler -E -x c - \| tail -n 1) 18 MINOR=$(echo __GNUC_MINOR__ \| $compiler -E -x c - \| tail -n 1) 19 PATCHLEVEL=$(echo __GNUC_PATCHLEVEL__ \| $compiler -E -x c - \| tail -n 1)`
D	Kconfig.include	`27 # Return y if the compiler supports <flag>, n otherwise 39 $(error-if,$(failure,command -v $(CC)),compiler '$(CC)' not found) 46 # $(m32-flag): -m32 if the compiler supports it, or an empty string otherwise. 47 # $(m64-flag): -m64 if the compiler supports it, or an empty string otherwise.`
/Linux-v5.10/scripts/coccinelle/misc/
D	uninitialized_var.cocci	`5 /// For any compiler warnings about uninitialized variables, just add 8 /// compiler warnings (e.g. "unused variable"). If the compiler thinks it 9 /// is uninitialized, either simply initialize the variable or make compiler 11 /// obviously redundant, the compiler's dead-store elimination pass will make`
/Linux-v5.10/include/linux/
D	compiler_types.h	`333 #define __diag_ignore(compiler, version, option, comment) \ argument 334 __diag_ ## compiler(version, ignore, option) 335 #define __diag_warn(compiler, version, option, comment) \ argument 336 __diag_ ## compiler(version, warn, option) 337 #define __diag_error(compiler, version, option, comment) \ argument 338 __diag_ ## compiler(version, error, option)`
/Linux-v5.10/Documentation/RCU/
D	rcu_dereference.rst	26 compiler from deducing the resulting pointer value. Please see 28 for an example where the compiler can in fact deduce the exact 32 The compiler simply knows too much about integral values to 50 "(x-(uintptr_t)x)" for char* pointers. The compiler is within its 89 explained, if the two pointers are equal, the compiler could 97 Because the compiler now knows that the value of "p" is exactly 112 compiler knows that the pointer is NULL, you had better 114 non-equal, the compiler is none the wiser. Therefore, 119 Since there are no subsequent dereferences, the compiler 171 - The pointers are not equal -and- the compiler does [all …]
D	lockdep.rst	`58 and compiler constraints. This is useful when the data 63 but retain the compiler constraints that prevent duplicating 98 barriers and compiler constraints, it generates better code than do the`
/Linux-v5.10/Documentation/kbuild/
D	gcc-plugins.rst	`10 compiler [1]_. They are useful for runtime instrumentation and static analysis. 17 Plugin source files have to be compilable by both a C and a C++ compiler as well 18 because gcc versions 4.5 and 4.6 are compiled by a C compiler, 19 gcc-4.7 can be compiled by a C or a C++ compiler, 20 and versions 4.8+ can only be compiled by a C++ compiler. 53 gcc-common.h and chooses the proper host compiler to build the plugins`
D	llvm.rst	28 The compiler used can be swapped out via ``CC=`` command line argument to ``make``. 38 A single Clang compiler binary will typically contain all supported backends, 43 ``CROSS_COMPILE`` is not used to prefix the Clang compiler binary, instead
/Linux-v5.10/Documentation/ia64/
D	ia64.rst	`21 compiler. And various software packages also compiled with an 22 IA-64 compliant GCC compiler. 35 compliant GCC compiler.`
/Linux-v5.10/arch/nios2/platform/
D	Kconfig.platform	`66 instruction. This will enable the -mhw-mul compiler flag. 72 instruction. Enables the -mhw-mulx compiler flag. 78 instruction. Enables the -mhw-div compiler flag. 86 the -mbmx compiler flag. 94 the -mcdx compiler flag. 99 Enables the -mcustom-fpu-cfg=60-1 compiler flag.`
/Linux-v5.10/Documentation/
D	memory-barriers.txt	139 appears to be maintained. Similarly, the compiler may also arrange the 244 Whether on DEC Alpha or not, the READ_ONCE() also prevents compiler 269 (*) It _must_not_ be assumed that the compiler will do what you want 271 WRITE_ONCE(). Without them, the compiler is within its rights to 319 in a given bitfield are protected by different locks, the compiler's 361 What is required is some way of intervening to instruct the compiler and the 623 Documentation/RCU/rcu_dereference.rst file: The compiler can and does 667 the compiler's ignorance from breaking your code. 701 are optional! Without the READ_ONCE(), the compiler might combine the 703 the compiler might combine the store to 'b' with other stores to 'b'. [all …]
/Linux-v5.10/Documentation/ABI/testing/
D	configfs-acpi	`49 - ASCII ASL compiler vendor ID 52 - ASL compiler version`
/Linux-v5.10/arch/arm/kernel/
D	unwind.c	`18 #warning Your compiler does not have EABI support. 20 #warning Change compiler or disable ARM_UNWIND option. 22 #warning Your compiler is too buggy; it is known to not compile ARM unwind support. 23 #warning Change compiler or disable ARM_UNWIND option.`
/Linux-v5.10/Documentation/core-api/
D	unaligned-memory-access.rst	83 Fortunately things are not too complex, as in most cases, the compiler 100 Fortunately, the compiler understands the alignment constraints, so in the 102 Therefore, for standard structure types you can always rely on the compiler 106 Similarly, you can also rely on the compiler to align variables and function 126 For a natural alignment scheme, the compiler would only have to add a single 131 structure type. This GCC-specific attribute tells the compiler never to 137 architectural alignment requirements. However, again, the compiler is aware
D	atomic_ops.rst	91 away entirely by the compiler or processor, and explicitly invoke the 92 appropriate compiler and/or memory barrier for each use case. Failure 94 different architectures or compiler optimizations, or even changes in 95 unrelated code which changes how the compiler optimizes the section 101 and WRITE_ONCE() macros should be used to prevent the compiler from using 110 If the compiler can prove that do_something() does not store to the 111 variable a, then the compiler is within its rights transforming this to 118 If you don't want the compiler to do this (and you probably don't), then 132 If the compiler can prove that do_something_with() does not store to the 133 variable a, then the compiler is within its rights to manufacture an [all …]
/Linux-v5.10/include/xen/interface/
D	version.h	`29 char compiler[64]; member`
/Linux-v5.10/Documentation/process/
D	volatile-considered-harmful.rst	`40 compiler might think it knows what will be in shared_data, but the 46 necessary. But the compiler would also be prevented from optimizing access 54 by locks, but one also does not want the compiler "optimizing" register 69 hyperthreaded twin processor; it also happens to serve as a compiler`
/Linux-v5.10/Documentation/features/debug/stackprotector/
D	arch-support.txt	`4 # description: arch supports compiler driven stack overflow protection`
/Linux-v5.10/arch/s390/
D	Kconfig	372 Cause the compiler to tune (-mtune) the generated code for a machine. 375 This option only changes how the compiler emits instructions, not the 568 Compile the kernel with the expoline compiler options to guard 571 Requires a compiler with -mindirect-branch=thunk support for full 650 This option enables the compiler option -mkernel-backchain if it 651 is available. If the option is available the compiler supports 653 frame size. With an old compiler a non-leaf function needs a 665 This option enables the compiler option -mstack-guard and 666 -mstack-size if they are available. If the compiler supports them 688 prompt "Emit compiler warnings for function with dynamic stack usage" [all …]
/Linux-v5.10/Documentation/x86/x86_64/
D	fsgs.rst	`31 thread and the compiler emits the FS: address prefix for accesses to these 125 FSGSBASE instructions compiler support 139 code and the compiler option -mfsgsbase has to be added. 192 In case the compiler does not support address spaces, inline assembly can`
/Linux-v5.10/tools/memory-model/Documentation/
D	simple.txt	`58 locking functions must carefully prevent both the CPU and the compiler 225 no ordering, but they do prevent the compiler from carrying out a number 238 Don't let the compiler trip you up 244 surprising amount of analysis, care, and knowledge about the compiler. 245 Yes, some decades ago it was not unfair to consider a C compiler to be 253 understanding of both the C standard and your compiler. Here are some 256 Who's afraid of a big bad optimizing compiler?`
/Linux-v5.10/arch/mips/alchemy/
D	Platform	`32 # compiler picks the board one. If they don't, it will make sure`
/Linux-v5.10/Documentation/arm/
D	arm.rst	`11 In order to compile ARM Linux, you will need a compiler capable of 13 a good compiler. Fortunately, you needn't guess. The kernel will report 14 an error if your compiler is a recognized offender. 36 CROSS_COMPILE=<your-path-to-your-compiler-without-gcc>`
/Linux-v5.10/tools/testing/selftests/rcutorture/bin/
D	kvm-recheck.sh	`80 echo Did you forget to switch your compiler with '--kmake-arg CC=<cc-that-supports-kcsan>'?`

12 3 4 5 6