| /openbsd-src/gnu/llvm/llvm/utils/lit/lit/ |
| H A D | BooleanExpression.py | 28 def evaluate(string, variables): argument 30 parser = BooleanExpression(string, set(variables)) 37 def __init__(self, string, variables): argument 39 self.variables = variables 40 self.variables.add('true') 102 self.value = any(regex.fullmatch(var) for var in self.variables) 152 variables = {'its-true', 'false-lol-true', 'under_score', 154 self.assertTrue(BooleanExpression.evaluate('true', variables)) 155 self.assertTrue(BooleanExpression.evaluate('its-true', variables)) 156 self.assertTrue(BooleanExpression.evaluate('false-lol-true', variables)) [all …]
|
| /openbsd-src/gnu/llvm/libcxx/utils/ |
| H A D | generate_header_tests.py | 85 def execute_script(script, variables): argument 92 exec(code, variables) 110 def produce(test_file, variables): argument 112 result = execute_script(script, variables) 133 variables = { 143 produce(test.joinpath('libcxx/assertions/headers_declare_verbose_abort.sh.cpp'), variables) 144 produce(test.joinpath('libcxx/clang_tidy.sh.cpp'), variables) 145 produce(test.joinpath('libcxx/double_include.sh.cpp'), variables) 146 produce(test.joinpath('libcxx/min_max_macros.compile.pass.cpp'), variables) 147 produce(test.joinpath('libcxx/modules_include.sh.cpp'), variables) [all …]
|
| /openbsd-src/usr.bin/pkg-config/OpenBSD/ |
| H A D | PkgConfig.pm | 59 variables => {}, 68 if (defined $self->{variables}{$name}) { 72 $self->{variables}{$name} = ($value =~ s/^\"|\"$//rg); 153 say $fh "$variable=", $self->{variables}{$variable}; 208 } elsif (defined $self->{variables}{$var}) { 209 return $self->{variables}{$var}; 215 # Expand all variables, unless the returned value is defined as an 256 my $v = $self->{variables}{$k}; 270 for my $name (keys %{$self->{variables}}) { 271 $self->{variables}{ [all...] |
| /openbsd-src/usr.bin/pkg-config/ |
| H A D | pkg-config | 60 my $variables = {}; 62 $variables->{pc_top_builddir} = $ENV{PKG_CONFIG_TOP_BUILD_DIR} // 65 $variables->{pc_sysrootdir} //= $ENV{PKG_CONFIG_SYSROOT_DIR}; 122 'define-variable=s' => $variables, 296 $variables->{lc($1)} = $ENV{$k}; 325 my $deps = $cfg->get_property($property, $variables); 409 my $e = $cfg->get_property($p, $variables); 459 my $value = $cfg->get_variable($v, $variables); 475 my $value = $cfg->get_property('Version', $variables); 495 my $l = $configs{$pkg}->get_property('Cflags', $variables); [all …]
|
| /openbsd-src/regress/usr.bin/pkg-config/ |
| H A D | Makefile | 90 variables-1 \ 91 variables-2 \ 92 variables-3 \ 93 variables-4 \ 94 variables-5 \ 95 variables-6 \ 96 variables-7 \ 616 variables-1: 619 @${VPCONFIG} --variable=plugindir variables 622 variables-2: [all …]
|
| /openbsd-src/gnu/llvm/clang/docs/ |
| H A D | BlockLanguageSpec.rst | 152 functions and global variables as one would expect, as well as static 153 local variables. [testme] 155 Local automatic (stack) variables referenced within the compound 172 The lifetime of variables declared in a Block is that of a function; 173 each activation frame contains a new copy of variables declared within 179 (nest) and all variables captured by any nested blocks are implicitly 183 Block variables at global or local static scope. 226 qualifier, :block-term:`__block`, for local variables. [testme: a 234 a Block_copy of a referencing Block. Such variables may be mutated as 235 normal variables are. [all …]
|
| H A D | Block-ABI-Apple.rst | 57 // imported variables 101 ``Block`` variables of global or ``static`` local variables. 126 b. The ``flags`` field is set to zero unless there are variables imported 170 variables, and variables marked ``__block``. In Objective-C, variables may 189 variables. 196 structure. Global variables are simply referenced and not considered as 199 Imported ``const`` copy variables 202 Automatic storage variables not marked with ``__block`` are imported as 320 Importing ``__attribute__((NSObject))`` variables 352 Imported ``__block`` marked variables [all …]
|
| /openbsd-src/gnu/llvm/llvm/utils/ |
| H A D | convert-constraint-log-to-z3.py | 52 variables = set() 55 variables.add(m.group()) 56 if len(variables) == 0: 58 for v in variables:
|
| /openbsd-src/gnu/llvm/lldb/examples/test/ |
| H A D | lldbtest-stderr | 7 Test that lldb persistent variables works correctly. ... ok 16 Test that lldb persistent variables works correctly. ... ok 25 Test that lldb persistent variables works correctly. ... ok 34 Test that lldb persistent variables works correctly. ... ok
|
| /openbsd-src/gnu/llvm/llvm/docs/ |
| H A D | StackSafetyAnalysis.rst | 9 The Stack Safety Analysis determines if stack allocated variables can be 13 unnecessary instrumentation of 'safe' variables. SafeStack is going to be the 16 'safe' variables can be defined as variables that can not be used out-of-scope 46 We expect that users can tolerate false classification of variables as 51 AddressSanitizer may help with this validation. We can instrument all variables
|
| /openbsd-src/gnu/llvm/llvm/docs/tutorial/MyFirstLanguageFrontend/ |
| H A D | LangImpl07.rst | 26 for an imperative language with mutable variables. 36 To understand why mutable variables cause complexities in SSA 78 In this example, the loads from the G and H global variables are 90 assignments to mutable variables?". The issue here is that LLVM 111 to talk about how LLVM represents stack variables. 115 operator. Notice how the type of the @G/@H global variables is actually 118 *name* actually refers to the address for that space. Stack variables 137 to functions, you can store it in other variables, etc. In our example 167 variables without the need to create Phi nodes at all: 209 pass is the answer to dealing with mutable variables, and we highly [all …]
|
| /openbsd-src/gnu/gcc/gcc/doc/ |
| H A D | interface.texi | 28 values. (GCC typically allocates variables of such types in 65 @cindex @code{longjmp} and automatic variables 66 If you use @code{longjmp}, beware of automatic variables. ISO C says that 67 automatic variables that are not declared @code{volatile} have undefined 69 because it is very difficult to restore register variables correctly, and 70 one of GCC's features is that it can put variables in registers without
|
| /openbsd-src/usr.bin/mail/ |
| H A D | vars.c | 57 vp->v_link = variables[h]; in assign() 58 variables[h] = vp; in assign() 129 for (vp = variables[hash(name)]; vp != NULL; vp = vp->v_link) in lookup()
|
| /openbsd-src/gnu/usr.bin/cvs/doc/ |
| H A D | cvs.info-9 | 158 * COMSPEC, environment variable: Environment variables. 196 * CVS_CLIENT_LOG, environment variable: Environment variables. 198 * CVS_IGNORE_REMOTE_ROOT, environment variable: Environment variables. 200 * CVS_RCMD_PORT, environment variable: Environment variables. 201 * CVS_RSH, environment variable: Environment variables. 204 * CVS_SERVER_SLEEP, environment variable: Environment variables. 209 * CVSIGNORE, environment variable: Environment variables. 210 * CVSREAD, environment variable: Environment variables. 223 * CVSWRAPPERS, environment variable <1>: Environment variables. 266 * Environment variables: Environment variables. [all …]
|
| /openbsd-src/usr.sbin/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…
|
| /openbsd-src/gnu/usr.bin/texinfo/info/ |
| H A D | variables.c | 208 REFERENCE **variables; in read_variable_name() local 211 variables = make_variable_completions_array (); in read_variable_name() 215 info_read_completing_in_echo_area (window, prompt, variables); in read_variable_name() 217 info_free_references (variables); in read_variable_name()
|
| /openbsd-src/gnu/lib/libstdc++/libstdc++/ |
| H A D | configure.target | 4 # It sets various shell variables based on the the target and the 11 # It uses the following shell variables as set by config.guess: 17 # It sets the following shell variables: 36 # It possibly modifies the following variables: 44 # variables that won't work, i.e., you do not need to explicitly set a 46 # *_include_dir variables.
|
| /openbsd-src/regress/bin/ksh/ |
| H A D | arith.t | 128 of variables recursively. 140 Check that variables can be used as array indices. 162 substitution to the values of variables. 176 substitution to arry indices inside the values of variables.
|
| /openbsd-src/gnu/llvm/llvm/cmake/modules/ |
| H A D | FindOCaml.cmake | 9 # If successful, the following variables will be defined: 21 # In any case, the following variables are defined: 25 # If successful, the following variables will be defined:
|
| H A D | ChooseMSVCCRT.cmake | 8 # CMAKE_C_FLAGS_* variables by default. To let the user 13 # 2. Replace the flags in both variables with the new flag via a regex. 14 # 3. set() the variables back into the cache so the changes 58 variables (LLVM_USE_CRT_DEBUG, etc) instead.")
|
| /openbsd-src/gnu/usr.bin/gcc/gcc/doc/ |
| H A D | interface.texi | 28 values. (GCC typically allocates variables of such types in 65 @cindex @code{longjmp} and automatic variables 66 If you use @code{longjmp}, beware of automatic variables. ISO C says that 67 automatic variables that are not declared @code{volatile} have undefined 69 because it is very difficult to restore register variables correctly, and 70 one of GCC's features is that it can put variables in registers without
|
| /openbsd-src/gnu/llvm/clang/ |
| H A D | NOTES.txt | 77 Blocks should not capture variables that are only used in dead code. 80 variables if they're referenced in evaluated code, even if that code 89 warn about non-POD variables that are referenced but not captured, but 99 - the parameter variables can safely be copied and repassed
|
| /openbsd-src/gnu/llvm/llvm/docs/CommandGuide/ |
| H A D | llvm-locstats.rst | 28 .. option:: --only-variables 30 calculate the location statistics only for local variables 84 -the number of debug variables processed: 6
|
| /openbsd-src/gnu/usr.bin/gcc/gcc/testsuite/objc.dg/ |
| H A D | private-1.m | 1 /* Test errors for accessing @private and @protected variables. */ 36 /* Private variables simply don't exist in the subclass. */
|
| /openbsd-src/gnu/llvm/lldb/source/Plugins/Platform/QemuUser/ |
| H A D | PlatformQemuUserProperties.td | 19 Desc<"Extra variables to add to the emulator environment.">; 23 Desc<"Extra variables to add to emulated target environment.">;
|