Home
last modified time | relevance | path

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

1234567

/linux-6.3-rc2/tools/memory-model/Documentation/
A Dcontrol-dependencies.txt6 help you prevent your compiler from breaking your code. However,
9 your own code, even in the absence of help from your compiler.
41 WRITE_ONCE() are optional. Without the READ_ONCE(), the compiler might
44 the compiler might convert the store into a load and a check followed
45 by a store, and this compiler-generated load would not be ordered by
56 In particular, although READ_ONCE() does force the compiler to emit a
90 assembly code, after all of the compiler and link-time optimizations
132 If MAX is compile-time defined to be 1, then the compiler knows that
179 does force the compiler to emit code for a given load, the compiler is
195 compiler cannot reorder volatile accesses and also cannot reorder
[all …]
A Daccess-marking.txt34 any sort of constraint on the compiler's choice of optimizations [2].
36 compiler's use of code-motion and common-subexpression optimizations.
41 data_race(READ_ONCE(a)), which will both restrict compiler optimizations
91 If it is necessary to both restrict compiler optimizations and disable
115 that provides the compiler much less scope for mischievous optimizations.
152 due to compiler-mangled reads, it can also tolerate the occasional
153 compiler-mangled write, at least assuming that the proper value is in
216 of how the compiler has been prevented from optimizing those accesses
237 As noted earlier, the goal is to prevent the compiler from destroying
288 If it is necessary to suppress compiler optimization and also detect
[all …]
A Dordering.txt190 compiler might then reasonably decide to transform "x = 1" and "y = 1"
222 The Linux kernel's compiler barrier is barrier(). This primitive
223 prohibits compiler code-motion optimizations that might move memory
226 used to prevent to compiler from moving code across an infinite loop:
432 However, control dependencies are easily destroyed by compiler
460 primitives required the compiler to emit the corresponding store
468 primitives required the compiler to emit the corresponding load
508 any number of compiler optimizations, many of which can break your
511 is required on an ongoing basis. The compiler-constraining barrier()
548 Who's afraid of a big bad optimizing compiler?
[all …]
A DREADME28 o You would like a detailed understanding of what your compiler can
54 Guide to preventing compiler optimizations from destroying
/linux-6.3-rc2/scripts/coccinelle/misc/
A Duninitialized_var.cocci7 /// For any compiler warnings about uninitialized variables, just add
10 /// compiler warnings (e.g. "unused variable"). If the compiler thinks it
11 /// is uninitialized, either simply initialize the variable or make compiler
13 /// obviously redundant, the compiler's dead-store elimination pass will make
/linux-6.3-rc2/Documentation/RCU/
A Drcu_dereference.rst29 for an example where the compiler can in fact deduce the exact
39 The compiler simply knows too much about integral values to
119 compiler knows that the pointer is NULL, you had better
121 non-equal, the compiler is none the wiser. Therefore,
126 Since there are no subsequent dereferences, the compiler
184 - The pointers are not equal *and* the compiler does
189 However, please note that if the compiler knows that the
192 compiler needs to deduce the value of the pointer.
251 /* The compiler decides that q->c is same as p->c. */
313 /* The compiler decides that q->c is same as p->c. */
[all …]
/linux-6.3-rc2/scripts/
A DKconfig.include27 # Return y if the compiler supports <flag>, n otherwise
39 $(error-if,$(failure,command -v $(CC)),C compiler '$(CC)' not found)
42 # Get the C compiler name, version, and error out if it is not supported.
44 $(error-if,$(success,test -z "$(cc-info)"),Sorry$(comma) this C compiler is not supported.)
61 # $(m32-flag): -m32 if the compiler supports it, or an empty string otherwise.
62 # $(m64-flag): -m64 if the compiler supports it, or an empty string otherwise.
/linux-6.3-rc2/include/linux/
A Dcompiler_types.h415 #define __diag_ignore(compiler, version, option, comment) \ argument
416 __diag_ ## compiler(version, ignore, option)
417 #define __diag_warn(compiler, version, option, comment) \ argument
418 __diag_ ## compiler(version, warn, option)
419 #define __diag_error(compiler, version, option, comment) \ argument
420 __diag_ ## compiler(version, error, option)
/linux-6.3-rc2/Documentation/ia64/
A Dia64.rst21 compiler. And various software packages also compiled with an
22 IA-64 compliant GCC compiler.
35 compliant GCC compiler.
/linux-6.3-rc2/arch/nios2/platform/
A DKconfig.platform67 instruction. This will enable the -mhw-mul compiler flag.
73 instruction. Enables the -mhw-mulx compiler flag.
79 instruction. Enables the -mhw-div compiler flag.
87 the -mbmx compiler flag.
95 the -mcdx compiler flag.
100 Enables the -mcustom-fpu-cfg=60-1 compiler flag.
/linux-6.3-rc2/Documentation/kbuild/
A Dgcc-plugins.rst10 compiler [1]_. They are useful for runtime instrumentation and static analysis.
16 Plugin source files have to be compilable by a C++ compiler.
39 compiler features that are neither in GCC nor Clang upstream. Once
45 upstream compiler support (in either GCC or Clang).
106 Run gcc (native or cross-compiler) to ensure plugin headers are detected::
/linux-6.3-rc2/Documentation/
A Dmemory-barriers.txt678 the compiler's ignorance from breaking your code.
801 equal to zero, in which case the compiler is within its rights to
846 the compiler to use the results.
861 compiler cannot reorder volatile accesses and also cannot reorder
863 of reasoning, the compiler might compile the two writes to 'b' as
1636 compiler that it doesn't know as much as it thinks it does:
1692 There is nothing to prevent the compiler from transforming
1868 compiler and the CPU from reordering them.
1877 compiler barrier in a UP compilation.
2078 the reordering, not the compiler. If the compiler (or, for
[all …]
/linux-6.3-rc2/Documentation/ABI/testing/
A Dconfigfs-acpi49 - ASCII ASL compiler vendor ID
52 - ASL compiler version
/linux-6.3-rc2/kernel/bpf/
A DKconfig7 # Used by archs to tell that they support BPF JIT compiler plus which
19 # Used by archs to tell that they want the BPF JIT compiler enabled by
41 bool "Enable BPF Just In Time compiler"
/linux-6.3-rc2/Documentation/dev-tools/
A Dkmsan.rst9 values. It is based on compiler instrumentation, and is quite similar to the
90 it, which can be helpful if we do not want the compiler to interfere with some
117 the only compiler that has KMSAN support. The kernel instrumentation pass is
135 instrumentation code inserted by the compiler (unless it is a stack variable
147 that takes one or more values the compiler generates code that calculates the
229 For every memory access the compiler emits a call to a function that returns a
243 The compiler makes sure that for every loaded value its shadow and origin
283 ``-fsanitize-memory-param-retval``, which makes the compiler check function
297 The compiler replaces calls to ``memcpy()``/``memmove()``/``memset()`` with the
309 For each use of a value the compiler emits a shadow check that calls
/linux-6.3-rc2/Documentation/core-api/
A Dunaligned-memory-access.rst83 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
/linux-6.3-rc2/include/xen/interface/
A Dversion.h29 char compiler[64]; member
/linux-6.3-rc2/lib/
A DKconfig.kmsan20 uninitialized values in the kernel. It is based on compiler
41 If the compiler supports -fsanitize-memory-param-retval, KMSAN will
A DKconfig.kasan56 # this variable to decide how the compiler should treat builtins.
59 The compiler is able to prefix memintrinsics with __asan or __hwasan.
142 Makes the compiler insert function calls that check whether the memory
150 Makes the compiler directly insert memory accessibility checks before
/linux-6.3-rc2/Documentation/process/
A Dvolatile-considered-harmful.rst40 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-6.3-rc2/Documentation/features/debug/stackprotector/
A Darch-support.txt4 # description: arch supports compiler driven stack overflow protection
/linux-6.3-rc2/Documentation/x86/x86_64/
A Dfsgs.rst31 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-6.3-rc2/tools/testing/selftests/arm64/mte/
A DMakefile32 $(warning compiler "$(CC)" does not support the ARMv8.5 MTE extension.)
/linux-6.3-rc2/Documentation/networking/
A Dfilter.rst51 internal compiler that generates a structure that can eventually be loaded
172 filters use Linux extensions that are not supported by libpcap's compiler,
174 libpcap's compiler, or iv) particular filter codes should be optimized
175 differently than libpcap's internal compiler does; then in such cases
512 JIT compiler
515 The Linux kernel has a built-in BPF JIT compiler for x86_64, SPARC,
517 CONFIG_BPF_JIT. The JIT compiler is transparently invoked for each
547 70 bytes emitted from JIT compiler (pass:3, flen:6)
574 70 bytes emitted from JIT compiler (pass:3, flen:6)
618 toolchain for developing and testing the kernel's JIT compiler.
[all …]
/linux-6.3-rc2/Documentation/rust/
A Darch-support.rst6 Currently, the Rust compiler (``rustc``) uses LLVM for code generation,

Completed in 28 milliseconds

1234567