| /freebsd-src/contrib/kyua/doc/ |
| H A D | kyua.conf.5.in | 37 Variables:
45 configuration variables.
46 There are configuration variables that have a special meaning to the runtime
49 and there are variables that only have meaning in the context of particular
54 variables, but the user has the freedom to implement any logic he desires
70 .Ss Runtime configuration variables
71 The following variables are internally recognized by
96 .Ss Test-suite configuration variables
97 Each test suite is able to recognize arbitrary configuration variables, and
99 Because the existence and naming of these variables depend
[all...] |
| /freebsd-src/sys/dev/bxe/ |
| H A D | ecore_hsi.h | 3577 … (0xFF<<0) /* BitField agg_vars1Various aggregative variables The state of the…
3579 … (0x1<<8) /* BitField agg_vars1Various aggregative variables The connection i…
3581 … (0x1<<9) /* BitField agg_vars1Various aggregative variables The connection i…
3583 … (0x1<<10) /* BitField agg_vars1Various aggregative variables The connection i…
3585 … (0x1<<11) /* BitField agg_vars1Various aggregative variables The connection i…
3587 … (0x1<<12) /* BitField agg_vars1Various aggregative variables ULP Rx SE counte…
3589 … (0x1<<13) /* BitField agg_vars1Various aggregative variables ULP Rx invalidat…
3591 … (0x3<<14) /* BitField agg_vars1Various aggregative variables Aux 4 counter fl…
3593 … (0x3<<16) /* BitField agg_vars1Various aggregative variables The connection Q…
3595 … (0x1<<18) /* BitField agg_vars1Various aggregative variables Enable decision …
[all …]
|
| /freebsd-src/contrib/bmake/unit-tests/ |
| H A D | var-scope-local.mk | 3 # Tests for target-local variables, such as ${.TARGET} or $@. These variables
5 # target. In contrast, global variables are typically created when the
8 # The 7 built-in target-local variables are listed in the manual page. They
10 # target-local variables can be defined in dependency lines like
15 # Target-local variables in a target rule
56 # Target-local variables in an inference rule
61 # Target-local variables in a chain of inference rules
73 # The target-local variables can be used in expressions, just like other
74 # variables. When these expressions are evaluated outside of a target, these
76 # these expressions to expand right in time when the target-local variables
[all …]
|
| H A D | directive-for-empty.mk | 17 # replacement creates the impression that .for variables were real variables,
30 # variables were real variables, calling 'empty' would work on them as well.
37 # The typical way of mistakenly using 'empty' with variables from .for loops
42 # Instead of the 'empty' function, the variables from .for loops can be
82 # An idea to work around the above problems is to collect the variables from
99 # that variables from .for loops can only affect expressions in the current
100 # file. If variables from .for loops were implemented as global variables,
117 # effect though. There are several modifiers that actually modify variables,
123 # TODO: Add code that demonstrates the current interaction between variables
|
| H A D | directive-export.mk | 32 # argument exported all global variables. This case could be triggered
38 # An empty argument means no additional variables to export.
43 # or for the ':sh' modifier, all variables that were marked for being exported
45 # running a child command, the marked-as-exported variables would need to be
47 # don't export the variables while preparing a child process, see
56 # that only subprocesses access the environment variables. The ':localtime'
66 _!= echo 'force exporting the environment variables'
|
| H A D | var-scope-local-legacy.mk | 3 # Tests for legacy target-local variables, such as ${<F} or ${@D}.
7 # as the target-specific variables are not available either. The expressions
13 # It's possible to define variables of the legacy name in the global or
14 # command line scope, and they override the target-local variables, leading to
23 # Only variables of length 2 can be legacy, this one cannot.
28 # variables, 'A' is not such a character.
|
| /freebsd-src/usr.bin/getconf/ |
| H A D | getconf.1 | 34 .Nd retrieve standard configuration variables
53 path or system configuration variables to the standard output.
59 variables to standard output.
63 all path configuration variables are reported for
68 all system configuration variables are reported using
75 configuration variables using
78 configuration variables using
90 variables use the same name as the manifest constants defined in
105 Variables retrieved from
162 variables provide information on the necessary compiler and linker flags
[all …]
|
| /freebsd-src/usr.sbin/ntp/doc/ |
| H A D | ntpq.8 | |
| /freebsd-src/contrib/ntp/ntpq/ |
| H A D | ntpq.mdoc.in | 30 variables can be assembled, with raw and pretty\-printed output
128 in requests to the server to read variables.
139 command allows variables and their optional values to be added to
145 command can be used to remove individual variables from the list,
148 command removes all variables from the
152 command displays the current list of optional variables.
174 variables which are recognized by
178 Variables which
294 Association ids are used to identify system, peer and clock variables.
295 System variables are assigned an association id of zero and system name
[all …]
|
| H A D | ntpq.1ntpqmdoc | 30 variables can be assembled, with raw and pretty\-printed output
128 in requests to the server to read variables.
139 command allows variables and their optional values to be added to
145 command can be used to remove individual variables from the list,
148 command removes all variables from the
152 command displays the current list of optional variables.
174 variables which are recognized by
178 Variables which
294 Association ids are used to identify system, peer and clock variables.
295 System variables are assigned an association id of zero and system name
[all …]
|
| H A D | ntpq.texi | 46 * System Variables::
47 * Peer Variables::
48 * Clock Variables::
59 The description on this page is for the NTPv4 variables.
61 …led using command line arguments. Requests to read and write arbitrary variables can be assembled…
134 The @code{addvars} command allows variables and optional values
138 The @code{rmvars} command can be used to remove individual variables
140 while the @code{clearlist} command removes all variables from the list.
201 Association IDs are used to identify system, peer and clock variables.
202 System variables are assigned an association ID of zero and system name space,
[all …]
|
| H A D | ntpq-opts.def | 148 variables can be assembled, with raw and pretty-printed output
247 in requests to the server to read variables.
258 command allows variables and their optional values to be added to
264 command can be used to remove individual variables from the list,
267 command removes all variables from the
271 command displays the current list of optional variables.
293 variables which are recognized by
297 Variables which
414 Association ids are used to identify system, peer and clock variables.
415 System variables ar
[all...] |
| /freebsd-src/sys/contrib/xen/ |
| H A D | platform.h | 40 /* IN variables. */
48 /* IN variables. */
74 /* IN variables. */
78 /* OUT variables. */
94 /* IN variables. */
104 /* IN variables. */
106 /* OUT variables. */
116 /* IN variables. */
128 /* IN variables. */
248 /* IN variables. */
[all …]
|
| /freebsd-src/contrib/llvm-project/llvm/tools/llvm-dwarfdump/ |
| H A D | Statistics.cpp | 26 /// calculated. The first category is the number of variables with 0% location
27 /// coverage, but the last category is the number of variables with 100%
37 /// This represents variables DIE offsets.
39 /// This maps function DIE offset to its variables.
79 /// contains variables, such as a compile unit).
87 /// Number of variables and parameters with location across all inlined
92 /// Number of arificial variables, parameters or members across all instances.
94 /// List of all Variables and parameters in this function.
108 /// Number of local variables.
110 /// Number of local variables wit
[all...] |
| /freebsd-src/contrib/llvm-project/llvm/lib/Target/AMDGPU/ |
| H A D | AMDGPULowerModuleLDSPass.cpp | 14 // The programming model is global variables, or equivalently function local
15 // static variables, accessible from kernels or other functions. For uses from
17 // memory required by all the variables combined, allocate them within that.
31 // do not alias, which permits only allocating variables they use
35 // struct instance. This duplicates the variables, accurately modelling their
48 // LDS variables with constant annotation or non-undef initializer are passed
52 // LDS variables that are always allocated at the same address can be found
55 // The simplest strategy possible is to group all LDS variables in a single
57 // variables are always at the same address. LDS is however a limited resource
69 // for variables tha
476 getAddressesOfVariablesInKernel(LLVMContext & Ctx,ArrayRef<GlobalVariable * > Variables,const DenseMap<GlobalVariable *,Constant * > & LDSVarsToConstantGEP) getAddressesOfVariablesInKernel() argument
502 buildLookupTable(Module & M,ArrayRef<GlobalVariable * > Variables,ArrayRef<Function * > kernels,DenseMap<Function *,LDSVariableReplacement> & KernelToReplacement) buildLookupTable() argument
[all...] |
| /freebsd-src/usr.sbin/efibootmgr/ |
| H A D | efibootmgr.8 | 90 These variables are numbered, each describing where to load the bootstrap
103 non-volatile variables.
135 Process but do not change any variables.
139 variable, include a set of environment variables for the loader to set after
141 Variables are of the form
150 will parse this area and set all variables found there.
154 path to the ESP device, derived from the EFI variables
208 related variables in the system:
222 variables, active or not.
227 The flag will also include any unreferenced (by BootOrder) variables
[all...] |
| /freebsd-src/contrib/bmake/ |
| H A D | bmake.1 | 223 option to print raw values of variables,
234 Let environment variables override global variables within makefiles.
383 the variables are printed one per line,
402 Note that loop-local and target-local variables, as well as values
403 taken temporarily by global variables during makefile processing, are
412 but all printed variables are always expanded to their complete value.
417 decides whether all variables are expanded or not.
423 Don't export variables passed on the command line to the environment
425 Variables passe
[all...] |
| H A D | make.1 | 223 option to print raw values of variables,
234 Let environment variables override global variables within makefiles.
383 the variables are printed one per line,
402 Note that loop-local and target-local variables, as well as values
403 taken temporarily by global variables during makefile processing, are
412 but all printed variables are always expanded to their complete value.
417 decides whether all variables are expanded or not.
423 Don't export variables passed on the command line to the environment
425 Variables passe
[all...] |
| /freebsd-src/contrib/tcsh/ |
| H A D | tw.color.c | 59 static Variable variables[] = { variable
90 #define nvariables (sizeof(variables)/sizeof(variables[0]))
226 variables[i].color = variables[i].defaultcolor; in init()
309 makecolor(&c, fg, bg, &variables[map[i]].color); in parseLSCOLORS()
380 if ((Char)variables[i].variable[0] == (v[0] & CHAR) && in parseLS_COLORS()
381 (Char)variables[i].variable[1] == (v[1] & CHAR)) in parseLS_COLORS()
385 getstring(&c, &v, &variables[i].color, ':'); in parseLS_COLORS()
429 Str *colorp = &variables[VFile].color; in print_color()
434 colorp = &variables[VDir].color; in print_color()
442 if (variables[i].suffix != NOS && in print_color()
[all …]
|
| /freebsd-src/contrib/llvm-project/openmp/runtime/src/ |
| H A D | kmp_environment.cpp | 2 * kmp_environment.cpp -- Handle environment variables OS-independently.
14 act of loading a DLL on Windows* OS makes any user-set environment variables
16 the env variables as they existed at the start of the run. JH 12/23/2002
27 getenv() function search for variables in C RTL environment only.
40 1. Set variables with putenv() function -- both C and Windows* OS on IA-32
44 2. Get variables with GetEnvironmentVariable() -- getenv() does not
45 search Windows* OS on IA-32 architecture, and can not see variables
101 variables (i.e. with putenv()) unavailable. getenv() apparently gets a in __kmp_env_get()
102 clean copy of the env variables as they existed at the start of the run. in __kmp_env_get()
178 // Dead code. I tried to put too many variables into Linux* OS in __kmp_env_set()
[all …]
|
| /freebsd-src/usr.bin/tip/tip/ |
| H A D | cu.1 | 197 List all variables and their values (if set).
242 variables are used to recognize end-of-file when reading, and specify
276 .Ss Variables
280 maintains a set of variables which control its operation.
281 Some of these variables are read-only to normal users (root is allowed
283 Variables may be displayed and set through the
286 The syntax for variables is patterned after
292 as an argument to the set command displays all variables readable by
302 Variables are numeric, string, character, or boolean values.
303 Boolean variables ar
[all...] |
| H A D | tip.1 | 198 List all variables and their values (if set).
292 variables are used to recognize end-of-file when reading, and specify
326 .Ss Variables
330 maintains a set of variables which control its operation.
331 Some of these variables are read-only to normal users (root is allowed
333 Variables may be displayed and set through the
336 The syntax for variables is patterned after
342 as an argument to the set command displays all variables readable by
352 Variables are numeric, string, character, or boolean values.
353 Boolean variables are set merely by specifying their name; they may be
[all …]
|
| /freebsd-src/contrib/llvm-project/lldb/source/Plugins/ExpressionParser/Clang/ |
| H A D | ClangExpressionVariable.h | 44 /// The expression parser uses variables in three different contexts:
46 /// First, it stores persistent variables along with the process for use in
47 /// expressions. These persistent variables contain their own data and are
50 /// Second, in an interpreted expression, it stores the local variables for
51 /// the expression along with the expression. These variables contain their
54 /// Third, in a JIT-compiled expression, it stores the variables that the
150 /// specific variables
155 /// Deallocate parser-specific variables
158 /// Access parser-specific variables
185 /// space for JIT-specific variables
[all …]
|
| /freebsd-src/contrib/ldns/ |
| H A D | README-Travis.md | 65 …he Autotools triplet, the OpenSSL triplet, the toolchain path, the tool variables, and the sysroot…
69 The first step sets environmental variables for the cross-compile using the Travis job. A typical j…
90 …variables `ANDROID_NDK_ROOT` and `ANDROID_SDK_ROOT`. This is an important step because the NDK and…
116 …`. The script is `sourced` so the variables in the script are available to the calling shell. The …
118 …cture to select by inspecting environmental variables set by Travis for the job. In particular, th…
183 …he Autotools triplet, the OpenSSL triplet, the toolchain path, the tool variables, and the sysroot…
187 The first step sets environmental variables for the cross-compile using the Travis job. A typical j…
219 …`. The script is `sourced` so the variables in the script are available to the calling shell. The …
221 …cture to select by inspecting environmental variables set by Travis for the job. In particular, th…
|
| /freebsd-src/contrib/unbound/ |
| H A D | README-Travis.md | 69 …he Autotools triplet, the OpenSSL triplet, the toolchain path, the tool variables, and the sysroot…
73 The first step sets environmental variables for the cross-compile using the Travis job. A typical j…
94 …variables `ANDROID_NDK_ROOT` and `ANDROID_SDK_ROOT`. This is an important step because the NDK and…
120 …`. The script is `sourced` so the variables in the script are available to the calling shell. The …
122 …cture to select by inspecting environmental variables set by Travis for the job. In particular, th…
185 …he Autotools triplet, the OpenSSL triplet, the toolchain path, the tool variables, and the sysroot…
189 The first step sets environmental variables for the cross-compile using the Travis job. A typical j…
221 …`. The script is `sourced` so the variables in the script are available to the calling shell. The …
223 …cture to select by inspecting environmental variables set by Travis for the job. In particular, th…
|