Searched refs:scope (Results 1 - 7 of 7) sorted by relevance

/seL4-camkes-master/projects/musllibc/src/thread/
H A Dpthread_attr_setscope.c3 int pthread_attr_setscope(pthread_attr_t *a, int scope) argument
5 switch (scope) {
H A Dpthread_attr_get.c32 int pthread_attr_getscope(const pthread_attr_t *restrict a, int *restrict scope) argument
34 *scope = PTHREAD_SCOPE_SYSTEM;
/seL4-camkes-master/projects/camkes-tool/camkes/parser/
H A Dscope.py38 you enter a nested scope and `close` every time you leave one. Within a
39 scope, `register` can be used to save an AST object by name. `lookup` is
42 entities are returned. When you close a scope, all registered entities at
93 for scope in reversed(self.scopes):
94 for candidate in scope[head].values():
100 # Construct a scope for the entity we've found and
128 all children is so they can be found in the penultimate scope when
139 # Suppress `__enter__` in our parent which would open another scope.
144 Construct a scope for resolution within an AST object.
148 # Create a new scope
[all...]
H A Dstage4.py33 from .scope import ForwardScopingContext, ScopingContext
64 # in the assembly scope to allow cross-assembly references.
99 # the assembly scope. This permits (backwards) references
137 scope = ScopingContext() variable in class:resolve.Resolver
138 scope.open()
140 [scope.register(y) for y in assembly.composition.children
147 end.instance = next(scope.lookup(end.instance.name, end.instance.type))
154 end.interface = next(scope.lookup(end.interface.name, end.interface.type))
/seL4-camkes-master/projects/util_libs/libplatsupport/plat_include/pc99/platsupport/plat/acpi/tables/
H A Ddmar.h47 // device scope structure
82 /* first device scope in "linked list" */
93 /* first device scope in "linked list" */
103 /* first device scope in "linked list" */
186 **** DMAR device scope helpers ****
189 /* Retrieve the first device scope for a DRHD table */
196 /* Retrieve the first device scope for an RMRR table */
203 /* Retrieve the first device scope for an ATSR table */
210 /* Retrieve the first device scope (table independant) */
222 return NULL; /* RHSA has no device scope */
230 acpi_dmar_next_dscope(acpi_dmar_remap_hdr_t* sh, acpi_dmar_dscope_t* scope) argument
[all...]
/seL4-camkes-master/tools/cogent/cogent/manual/
H A Dcogent-manual.tex999 is matched with a value, the value is bound to \code{x}. This means that in a certain \textit{scope}, the value can be referenced by denoting
1318 also inferred for every occurence of the variable as a term in its scope.
1787 For every \textit{Alternative} the \textit{Expression} is called the \textit{scope} of the variables occurring in
1880 \textit{LetExpression}, it is the scope of the variables in IP.
1887 where the bound value is used as the second field value. The tuple expression is the scope of variable \code{x}.
1895 as described in Section~\ref{pat-rec}. Then it uses them in their scope which is a tuple term.
1995 When a variable should be observed, an expression must be specified as scope of the observation. The readonly
1996 value may be freely used in this scope, but it may not escape from it. Syntactically, an expression which may
1997 be the scope of a variable observation is called an \textit{observable expression}.
2013 In both cases one or more observed variables are specified at the \textit{end} of the observation scope
[all...]
/seL4-camkes-master/tools/cogent/cogent/doc/
H A Ddoc.tex495 The scope of the read-only \inlinecogent{obj} is in the \inlinecogent{let}-binding (the expression on the RHS of the \inlinecogent{=} in
498 Note that the scope of the read-only
709 into scope. Syntax \code{\#\{...\}} (the \code{...} is meta-syntax) is
744 \code{let}, \code{if} and case distinction. The scope of bang'ed variables are highlighted in the following

Completed in 57 milliseconds