| /openbmc/openbmc-tools/dbus_sensor_tester/ |
| H A D | meson.build | 30 optimization = get_option('optimization') variable
32 summary('Optimization',optimization, section : 'Build Info')
34 # Disable lto when compiling with no optimization
35 if(get_option('optimization') == '0')
37 message('Disabling lto & its supported features as optimization is disabled')
|
| /openbmc/linux/tools/testing/selftests/ftrace/test.d/kprobe/ |
| H A D | kprobe_opt_types.tc | 19 DEFAULT=$(cat /proc/sys/debug/kprobes-optimization)
20 echo 1 > /proc/sys/debug/kprobes-optimization
29 echo "$DEFAULT" > /proc/sys/debug/kprobes-optimization
33 echo "$DEFAULT" > /proc/sys/debug/kprobes-optimization
|
| /openbmc/linux/Documentation/trace/ |
| H A D | kprobes.rst | 54 probes work and how jump optimization works. They explain certain
169 How Does Jump Optimization Work?
181 When a probe is registered, before attempting this optimization,
221 Pre-optimization
242 Optimization subsection
251 of kprobe optimization supports only kernels with CONFIG_PREEMPT=n [4]_.
262 the optimization is complete, the kprobe is just dequeued from the
263 optimized list. If the optimization has been done, the jump is
273 .. [4] This optimization-safety checking may be replaced with the
278 The jump optimization changes the kprobe's pre_handler behavior.
[all …]
|
| /openbmc/linux/Documentation/process/ |
| H A D | volatile-considered-harmful.rst | 15 to suppress optimization, which is almost never what one really wants to
19 all optimization-related problems in a more efficient way.
23 unwanted optimization. If they are being used properly, there will be no
42 forget anything it knows. There will be no optimization problems with
59 optimization, so, once again, volatile is unnecessary.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/rsyslog/librelp/ |
| H A D | 0001-Fix-function-inline-errors-in-debug-optimization-Og.patch | 4 Subject: [PATCH] Fix function inline errors in debug optimization (-Og)
6 Compiler does not inline any functions when using debug optimization (-Og).
7 Hence, remove -Winline flag when compiling with debug optimization.
|
| /openbmc/bmcweb/ |
| H A D | meson.build | 36 optimization = get_option('optimization') variable
38 summary('Optimization', optimization, section: 'Build Info')
53 # Disable lto when compiling with no optimization
54 if (get_option('optimization') == '0')
56 message('Disabling lto & its supported features as optimization is disabled')
130 if (get_option('b_lto') == true and get_option('optimization') != '0')
|
| H A D | HEADERS.md | 46 - Reduce the bmcweb binary size to the point where link time optimization is not
48 link time optimization, which, as of this time is required to keep bmcweb code
|
| /openbmc/linux/arch/x86/ |
| H A D | Kconfig.cpu | 2 # Put here option for CPU selection and depending optimization
103 copy optimization, compiles the kernel with optimization flags
164 some extended instructions, and passes appropriate optimization
172 some extended instructions, and passes appropriate optimization
180 optimization flags to GCC.
187 like a 586 with TSC, and sets some GCC optimization flags (like a
346 # P6_NOPs are a relatively minor optimization that require a family >=
354 # the right-hand clause are the cores that benefit from this optimization.
|
| /openbmc/openpower-vpd-parser/ |
| H A D | meson.build | 17 # Disable FORTIFY_SOURCE when compiling with no optimization
18 if(get_option('optimization') == '0')
20 message('Disabling FORTIFY_SOURCE as optimization is set to 0')
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/amdzen2/ |
| H A D | floating-point.json | 71 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
77 …optimization (have Z-bit either set or pass). This is a dispatch based speculative event, and is u…
83 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
89 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
|
| /openbmc/openbmc/meta-openembedded/meta-oe/licenses/ |
| H A D | GPL-2.0-with-lmbench-restriction | 74 subsystem, then the costs of the optimization are hidden and readers
75 will mistakenly believe that the optimization is a good idea. By
77 detect that the optimization improved the subsystem performance
79 to make an informed decision as to the merits of the optimization.
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/amdzen3/ |
| H A D | floating-point.json | 70 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
76 …optimization (have Z-bit either set or pass). This is a dispatch based speculative event, and is u…
82 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
88 …ful for measuring the effectiveness of the Move elimination and Scalar code optimization schemes.",
|
| /openbmc/linux/arch/powerpc/purgatory/ |
| H A D | Makefile | 8 # When profile-guided optimization is enabled, llvm emits two different
10 # optimization flags.
|
| /openbmc/u-boot/board/varisys/cyrus/ |
| H A D | README | 5 They currently disable size optimization in order to avoid a relocation
7 optimization is not currently important.
|
| /openbmc/linux/tools/power/acpi/ |
| H A D | Makefile.config | 61 # use '-Os' optimization if available, else use -O2
62 OPTIMIZATION := $(call cc-supports,-Os,-O2)
87 CFLAGS += $(OPTIMIZATION) -fomit-frame-pointer
|
| /openbmc/linux/include/drm/ |
| H A D | drm_cache.h | 55 * only, but permits an optimization to be enabled in some cases, where in drm_arch_can_wc_memory()
63 * case. However, on ARM and arm64, enabling this optimization on a in drm_arch_can_wc_memory()
67 * optimization entirely for ARM and arm64. in drm_arch_can_wc_memory()
|
| /openbmc/openbmc/poky/meta/conf/machine/include/mips/ |
| H A D | tune-octeon.inc | 7 TUNEVALID[octeon2] = "Enable optimization related to octeon2 support"
21 TUNEVALID[octeon3] = "Enable optimization related to octeon3 support"
|
| /openbmc/linux/tools/perf/pmu-events/arch/x86/amdzen1/ |
| H A D | floating-point.json | 172 …r measuring the effectiveness of the Move elimination and Scalar code optimization schemes. Number…
178 …"BriefDescription": "Number of Ops that are candidates for optimization (have Z-bit either set or …
179 …of the Move elimination and Scalar code optimization schemes. Number of Ops that are candidates fo…
186 …r measuring the effectiveness of the Move elimination and Scalar code optimization schemes. Number…
193 …r measuring the effectiveness of the Move elimination and Scalar code optimization schemes. Number…
|
| /openbmc/linux/scripts/ |
| H A D | Makefile.clang | 31 # certain optimization flags it knows it has not implemented.
35 CLANG_FLAGS += -Werror=ignored-optimization-argument
|
| /openbmc/linux/arch/alpha/include/asm/ |
| H A D | elf.h | 20 #define R_ALPHA_LITERAL 4 /* GP relative 16 bit w/optimization */
21 #define R_ALPHA_LITUSE 5 /* Optimization hint for LITERAL */
130 specific libraries for optimization. This is more specific in
|
| /openbmc/openbmc/meta-security/meta-tpm/recipes-tpm2/ibmswtpm2/files/ |
| H A D | tune-makefile.patch | 1 1) Allow recipe to overide optimization.
5 397 | # warning _FORTIFY_SOURCE requires compiling with optimization (-O)
|
| /openbmc/linux/Documentation/staging/ |
| H A D | static-keys.rst | 91 optimization.
100 In order to make use of this optimization you must first define a key::
184 to take advantage of this optimization. If there is no architecture support, we
248 Without the jump label optimization it looks like::
327 this optimization is about reducing the number of branches. In addition, we've
|
| /openbmc/linux/arch/x86/kernel/fpu/ |
| H A D | xstate.h | 109 * supports modified optimization which is not supported by XSAVE.
230 * This optimization is user-visible. Only use for states where
233 * Users of buffers produced with this optimization must check XSTATE_BV
253 * We don't use modified optimization because xrstor/xrstors might track
|
| /openbmc/linux/arch/x86/purgatory/ |
| H A D | Makefile | 17 # When profile-guided optimization is enabled, llvm emits two different
19 # optimization flags.
|
| /openbmc/phosphor-debug-collector/ |
| H A D | meson.build | 56 # Disable FORTIFY_SOURCE when compiling with no optimization
57 if(get_option('optimization') == '0')
59 message('Disabling FORTIFY_SOURCE as optimization is set to 0')
|