Home
last modified time | relevance | path

Searched refs:statement (Results 1 – 19 of 19) sorted by relevance

/tools/perf/util/scripting-engines/
A DBuild6 …-undef -Wno-switch-default -Wno-bad-function-cast -Wno-declaration-after-statement -Wno-switch-enum
8 # -Wno-declaration-after-statement: The python headers have mixed code with declarations (decls aft…
9 …arameter -Wno-shadow -Wno-deprecated-declarations -Wno-switch-enum -Wno-declaration-after-statement
/tools/perf/scripts/python/Perf-Trace-Util/
A DBuild3 # -Wno-declaration-after-statement: The python headers have mixed code with declarations (decls aft…
4 …s -Wno-strict-prototypes -Wno-unused-parameter -Wno-nested-externs -Wno-declaration-after-statement
/tools/testing/selftests/user_events/
A Duser_events_selftests.h97 #define USER_EVENT_FIXTURE_SETUP(statement, umount) do { \ argument
105 SKIP(statement, "Skipping due to: %s", message); \
/tools/memory-model/Documentation/
A Dcontrol-dependencies.txt50 the original example by eliminating the "if" statement as follows:
60 identical stores on both branches of the "if" statement as follows:
158 Please note once again that each leg of the "if" statement absolutely
161 "if" statement, destroying the control dependency's ordering properties.
183 else-clause of the "if" statement in question. In particular, they do
184 not necessarily order the code following the entire "if" statement:
214 to code following that "if" statement.
226 (*) If both legs of the "if" statement contain identical stores to
230 barrier() at beginning and end of each leg of the "if" statement
247 of the "if" statement containing the control dependency, including
[all …]
A Dlocking.txt26 Note that this statement is a bit stronger than "Any CPU holding a
60 subsequently acquires this same lock. This converse statement is
A Dlitmus-tests.txt310 LKMM supports the C-language "if" statement, which allows modeling of
343 P1()'s "if" statement on line 10 works as expected, so that line 11 is
360 However, there is no "while" statement due to the fact that full
436 statement on line 25 shows how to cause herd7 to display additional
965 up before the "if" statement, since the compiler has
1052 not supported. The "switch" statement can be emulated by the
1053 "if" statement. The "do", "for", and "while" statements can
A Drecipes.txt71 CPU before it released that same lock. Note that this statement is a bit
A Dexplanation.txt386 both branches of an "if" statement store the same value to the same
469 dependency if Y syntactically lies within an arm of an if statement and
471 dependency (or similarly for a switch statement). Simple example:
1753 time with statement labels added:
1921 given the situation outlined earlier (with statement labels added):
2318 pattern (with fences and statement labels, but without the conditional
A Dordering.txt417 that is executed only by one of the legs of that "if" statement.
/tools/perf/scripts/perl/Perf-Trace-Util/
A DBuild3 …cls -Wno-strict-prototypes -Wno-bad-function-cast -Wno-declaration-after-statement -Wno-switch-enum
/tools/memory-model/litmus-tests/
A Ddep+plain.litmus10 * conditional of P0()'s if-statement creates a control dependency
A DREADME130 statement, only those registers and locations mentioned in the
/tools/power/acpi/
A DMakefile.config66 WARNINGS += $(call cc-supports,-Wdeclaration-after-statement)
/tools/power/cpupower/
A DMakefile128 WARNINGS += $(call cc-supports,-Wdeclaration-after-statement)
/tools/scripts/
A DMakefile.include24 EXTRA_WARNINGS += -Wdeclaration-after-statement
/tools/testing/selftests/
A Dkselftest_harness.h124 #define SKIP(statement, fmt, ...) do { \ argument
133 statement; \
/tools/objtool/Documentation/
A Dobjtool.txt236 a) the jump is part of a switch statement; or
288 uses an inline asm() statement which has a "call" instruction. An
289 asm() statement with a call instruction must declare the use of the
/tools/testing/ktest/
A Dktest.pl946 my $statement = "$lval $cmp $rval";
947 my $ret = eval $statement;
/tools/perf/util/
A DBuild251 CFLAGS_demangle-rust-v0.o += -Wno-shadow -Wno-declaration-after-statement \

Completed in 23 milliseconds