Home
last modified time | relevance | path

Searched refs:variables (Results 1 – 25 of 412) sorted by relevance

12345678910>>...17

/minix3/usr.bin/make/unit-tests/
H A Dposix1.exp11 Local variables
16 Directory and filename parts of local variables
51 Local variables
56 Directory and filename parts of local variables
97 Local variables
102 Directory and filename parts of local variables
144 Local variables
149 Directory and filename parts of local variables
/minix3/external/bsd/llvm/dist/clang/docs/
H A DBlockLanguageSpec.rst152 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 DBlock-ABI-Apple.rst56 // imported variables
92 ``Block`` variables of global or ``static`` local variables.
117 b. The ``flags`` field is set to zero unless there are variables imported
161 variables, and variables marked ``__block``. In Objective-C, variables may
180 variables.
187 structure. Global variables are simply referenced and not considered as
190 Imported ``const`` copy variables
193 Automatic storage variables not marked with ``__block`` are imported as
311 Importing ``__attribute__((NSObject))`` variables
343 Imported ``__block`` marked variables
[all …]
/minix3/crypto/external/bsd/heimdal/dist/lib/hx509/
H A Dsel-gram.y65 %type <expr> variable variables
109 variable: '%' '{' variables '}' { $$ = $3; }
112 variables: IDENTIFIER '.' variables {
/minix3/external/bsd/llvm/dist/clang/test/SemaObjC/
H A Dno-ivar-in-interface-block.m6 …@protected int P_IVAR; // expected-warning {{declaration of instance variables in the interface i…
8 …@public int PU_IVAR; // expected-warning {{declaration of instance variables in the interface …
10 …@private int PRV_IVAR; // expected-warning {{declaration of instance variables in the interface…
H A Divar-in-class-extension-error.m7 int _p0; // expected-error {{instance variables may not be placed in class extension}}
13 int _p1; // expected-error {{instance variables may not be placed in categories}}
H A Darc-decls.m39 __autoreleasing id X; // expected-error {{global variables cannot have __autoreleasing ownership}}
40 __autoreleasing NSError *E; // expected-error {{global variables cannot have __autoreleasing owners…
43 extern id __autoreleasing X1; // expected-error {{global variables cannot have __autoreleasing owne…
48 …static id __autoreleasing X1; // expected-error {{global variables cannot have __autoreleasing own…
49 …extern id __autoreleasing E; // expected-error {{global variables cannot have __autoreleasing owne…
112 …ownership(none))) S2 {}; // expected-error {{'objc_ownership' attribute only applies to variables}}
H A Dblock-on-method-param.m6 …))) id)errorp; // expected-error {{__block attribute not allowed, only allowed on local variables}}
10 …) id)errorp {} // expected-error {{__block attribute not allowed, only allowed on local variables}}
H A Dconflicting-ivar-test-1.m24 int IVAR1; // expected-error {{inconsistent number of instance variables specified}}
49 int IVAR1; // expected-error {{inconsistent number of instance variables specified}}
/minix3/external/bsd/llvm/dist/llvm/docs/tutorial/
H A DLangImpl7.rst26 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 …]
H A DOCamlLangImpl7.rst26 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 …]
/minix3/external/bsd/llvm/dist/llvm/test/CodeGen/SystemZ/
H A Dla-03.ll21 ; Test loads of external variables, which must go via the GOT.
29 ; Check loads of locally-defined normal-visibility variables, which might
38 ; Check loads of protected variables, which in the small code model
47 ; ...likewise hidden variables.
H A Dla-02.ll23 ; Test loads of external variables. There is no guarantee that the
32 ; ...likewise locally-defined normal-visibility variables.
40 ; ...likewise protected variables.
48 ; ...likewise hidden variables.
/minix3/external/bsd/byacc/dist/
H A DNOTES4 use exactly six register variables is that Berkeley Yacc was
5 developed on a VAX using PCC. PCC placed at most six variables
7 variables most belonged in registers. Changes in machines and
/minix3/external/bsd/llvm/dist/llvm/cmake/modules/
H A DLLVMParseArguments.cmake5 # several variables. The first argument to PARSE_ARGUMENTS is a prefix to put on
6 # all variables it creates. The second argument is a list of names, and the
14 # options is OPTION1;OPTION2, then PARSE_ARGUMENTS will create the variables
15 # MY_MACRO_OPTION1 and MY_MACRO_OPTION2. These variables will be set to true if
37 # PARSE_ARGUMENTS creates 7 variables and sets them as follows:
H A DFindOCaml.cmake9 # 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 DChooseMSVCCRT.cmake8 # 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.")
/minix3/external/bsd/llvm/dist/clang/test/SemaOpenCL/
H A Dstorageclass.cl5 int X = 0; // expected-error{{global variables must have a constant address space qualifier}}
9 static int X = 5; // expected-error{{variables in function scope cannot be declared static}}
/minix3/external/bsd/llvm/dist/llvm/tools/llvm-config/
H A DBuildVariables.inc.in1 //===-- BuildVariables.inc.in - llvm-config build variables -*- C++ -*-----===//
10 // This file is configured by the build system to define the variables
/minix3/external/bsd/pkg_install/dist/lib/
H A Dvar.c66 var_copy_list(const char *buf, const char **variables) in var_copy_list() argument
81 for (i=0; variables[i]; i++) { in var_copy_list()
82 if (var_cmp(buf, len, variables[i], in var_copy_list()
83 strlen(variables[i])) != NULL) { in var_copy_list()
/minix3/external/bsd/llvm/dist/llvm/test/CodeGen/X86/
H A Dalignment.ll13 ; Common variables should not get rounded up to the preferred alignment (16) if
36 ; Common variables should not get rounded up to the preferred alignment (16) if
/minix3/crypto/external/bsd/openssl/lib/libdes/
H A Ddes_modes.pod65 The use of different starting variables prevents the same plaintext
91 The chaining operation makes the ciphertext variables dependent on the
92 current and all preceding variables and therefore j-bit variables are
97 The use of different starting variables prevents the same plaintext
117 An error will affect the current and the following ciphertext variables.
146 The use of different start variables values prevents the same
/minix3/crypto/external/bsd/openssl/dist/doc/crypto/
H A Ddes_modes.pod67 The use of different starting variables prevents the same plaintext
93 The chaining operation makes the ciphertext variables dependent on the
94 current and all preceding variables and therefore j-bit variables are
99 The use of different starting variables prevents the same plaintext
119 An error will affect the current and the following ciphertext variables.
148 The use of different start variables values prevents the same
/minix3/external/bsd/llvm/dist/llvm/docs/CommandGuide/
H A Dllvm-extract.rst17 :program:`llvm-extract` will also remove unreachable global variables,
48 specified multiple times to extract multiple global variables at once.
53 bitcode. All global variables matching the regular expression will be
/minix3/external/bsd/llvm/dist/clang/
H A DNOTES.txt84 Blocks should not capture variables that are only used in dead code.
87 variables if they're referenced in evaluated code, even if that code
96 warn about non-POD variables that are referenced but not captured, but
106 - the parameter variables can safely be copied and repassed

12345678910>>...17