Home
last modified time | relevance | path

Searched refs:compound (Results 1 – 25 of 116) sorted by relevance

12345

/openbsd-src/gnu/usr.bin/perl/cpan/podlators/t/data/snippets/man/
H A Dguesswork-none10 The hyphens-in-compound-words shouldn't be escaped, but e-mail should be.
21 The hyphens-in-compound-words shouldn't be escaped, but e\-mail should be.
H A Dguesswork-all10 The hyphens-in-compound-words shouldn't be escaped, but e-mail should be.
21 The hyphens-in-compound-words shouldn't be escaped, but e\-mail should be.
H A Dguesswork7 The hyphens-in-compound-words shouldn't be escaped, but e-mail should be.
18 The hyphens-in-compound-words shouldn't be escaped, but e\-mail should be.
H A Dguesswork-partial10 The hyphens-in-compound-words shouldn't be escaped, but e-mail should be.
21 The hyphens-in-compound-words shouldn't be escaped, but e\-mail should be.
/openbsd-src/gnu/gcc/gcc/
H A Dc-common.def28 /* A COMPOUND_LITERAL_EXPR represents a C99 compound literal. The
32 the compound literal. */
/openbsd-src/gnu/llvm/clang/docs/
H A DBlockLanguageSpec.rst148 The compound statement body establishes a new lexical scope within
149 that of its parent. Variables used within the scope of the compound
155 Local automatic (stack) variables referenced within the compound
252 The compound statement of a Block is treated much like a function body
276 scope of the compound statement. These variables are implicitly
343 leaves the compound statement that contains the Block literal
H A DClangTransformerTutorial.rst338 of rules that rewrite compound statements, where one rule handles the case of an
339 empty compound statement and the other handles non-empty compound statements.
349 The second rule does not need to explicitly specify that the compound statement
H A DIntroductionToTheClangAST.rst73 of "``f``". The body of "``f``" is a `compound
H A DBlock-ABI-Apple.rst110 any) to the ``Block`` and executes the ``Block`` compound statement.
480 A ``Block`` that uses a ``__block`` variable in its compound statement body must
708 and within the compound statement:
H A DReleaseNotes.rst299 - Implemented `P2324R2: Support label at end of compound statement <https://wg21.link/p2324r2>`_.
314 all compound assignments operations on volatile qualified variables.
334 so labels can placed everywhere inside a compound statement.
691 evaluating a compound assignment with remainder as operand.
/openbsd-src/gnu/usr.bin/gcc/gcc/
H A Dc-common.def109 /* A COMPOUND_LITERAL_EXPR represents a C99 compound literal. The
113 the compound literal. */
H A Dc-parse.in255 /* Number of statements (loosely speaking) and compound statements
673 pedwarn ("ISO C89 forbids compound literals");
2009 some labels) that can form the body of a compound statement.
2019 pedwarn ("deprecated use of label at end of compound statement");
2428 also at the end of a compound statement. */
/openbsd-src/gnu/llvm/clang/lib/StaticAnalyzer/
H A DREADME.txt78 corresponding lazy compound value if the variable is not a reference, and
79 bind the variable region to the lazy compound value. If the variable
/openbsd-src/gnu/gcc/gcc/doc/
H A Dtree-ssa.texi213 @code{INDIRECT_REF} or a compound lvalue as described below.
233 Currently compound lvalues involving array and structure field references
584 DECL_SAVED_TREE -> compound-stmt
586 compound-stmt: STATEMENT_LIST
603 BIND_EXPR_BODY -> compound-stmt
607 op1 -> compound-stmt
608 op2 -> compound-stmt
635 op0 -> compound-stmt
638 op0 -> compound-stmt
639 op1 -> compound-stmt
[all …]
/openbsd-src/gnu/llvm/clang/include/clang/Basic/
H A DDiagnosticParseKinds.td96 "compound literals are a C99-specific feature">, InGroup<C99>;
251 "expected '{' in compound literal">;
299 "label at end of compound statement is a C2x extension">,
302 "label at end of compound statement is a C++2b extension">,
305 "label at end of compound statement is incompatible with C standards before C2x">,
308 "label at end of compound statement is incompatible with C++ standards before C++2b">,
850 "'noexcept' can only be used in a compound requirement (with '{' '}' around "
1217 // - #pragma restricted to file scope or start of compound statement
1220 "compound statement">;
1226 // statements inside a compound statement.
H A DDiagnosticGroups.td49 def GNUCompoundLiteralInitializer : DiagGroup<"gnu-compound-literal-initializer">;
56 def CompoundTokenSplitByMacro : DiagGroup<"compound-token-split-by-macro">;
57 def CompoundTokenSplitBySpace : DiagGroup<"compound-token-split-by-space">;
58 def CompoundTokenSplit : DiagGroup<"compound-token-split",
/openbsd-src/gnu/llvm/llvm/lib/Target/Hexagon/
H A DHexagon.td81 def FeatureCompound: SubtargetFeature<"compound", "UseCompound", "true",
82 "Use compound instructions">;
/openbsd-src/gnu/usr.bin/gcc/gcc/java/
H A Dparse.c8037 tree compound = NULL_TREE; local
8050 compound = add_stmt_to_compound (compound, NULL_TREE, current);
8060 compound = encapsulate_with_try_catch (0, exception_type_node, compound,
8068 java_method_add_stmt (mdecl, compound);
11744 tree compound = TREE_VALUE (list); local
11756 TREE_OPERAND (compound, 1)
12413 tree thisn_assign, compound = NULL_TREE; local
12492 compound = add_stmt_to_compound (compound, NULL_TREE, thisn_assign);
12496 compound = add_stmt_to_compound (compound, NULL_TREE,
12502 compound = add_stmt_to_compound (compound, NULL_TREE,
[all …]
H A Dparse.y4472 tree compound = NULL_TREE; local
4485 compound = add_stmt_to_compound (compound, NULL_TREE, current);
4495 compound = encapsulate_with_try_catch (0, exception_type_node, compound,
4503 java_method_add_stmt (mdecl, compound);
8179 tree compound = TREE_VALUE (list); local
8191 TREE_OPERAND (compound, 1)
8848 tree thisn_assign, compound = NULL_TREE; local
8927 compound = add_stmt_to_compound (compound, NULL_TREE, thisn_assign);
8931 compound = add_stmt_to_compound (compound, NULL_TREE,
8937 compound = add_stmt_to_compound (compound, NULL_TREE,
[all …]
/openbsd-src/games/hack/
H A Dhelp112 A compound option is endgame; it is followed by a description
/openbsd-src/gnu/usr.bin/perl/pod/
H A Dperlunicode.pod435 All Unicode-defined character properties may be written in these compound forms
510 The compound way of writing these is like C<\p{General_Category=Number}>
599 This property is always written in the compound form.
619 can be specified with the compound form like
626 written in the compound form. Prior to Perl v5.26, the single form
691 without using the compound form mentioned
719 Block names are matched in the compound form, like C<\p{Block: Arrows}> or
756 Unicode defines all its properties in the compound form, so all single-form
759 the compound form. And quite a few of these are actually recommended by Unicode
763 synonyms for compound
[all...]
H A Dperlsyn.pod115 C<do {}> that I<look> like compound statements, but aren't--they're just
233 X<statement, compound> X<block> X<bracket, curly> X<curly bracket> X<brace>
252 The following compound statements may be used to control flow:
359 kinds of compound statements. These are introduced by a keyword which
/openbsd-src/gnu/llvm/libcxx/include/experimental/
H A Dsimd279 // compound assignment [simd.cassign]
638 // simd_mask compound assignment [simd.mask.cassign]
1493 // compound assignment [simd.cassign]
1563 // simd_mask compound assignment [simd.mask.cassign]
/openbsd-src/gnu/usr.bin/gcc/gcc/doc/
H A Dextend.texi489 A compound statement enclosed in parentheses may appear as an expression
493 Recall that a compound statement is a sequence of statements surrounded
508 The last thing in the compound statement should be an expression
1026 @cindex compound expressions as lvalues
1027 @cindex expressions, compound, as lvalues
1042 For example, a compound expression can be assigned, provided the last
1051 Similarly, the address of the compound expression can be taken. These two
1606 @cindex compound literals
1607 @c The GNU C name for what C99 calls compound literals was "constructor expressions".
1609 ISO C99 supports compound literals. A compound literal looks like
[all …]
/openbsd-src/gnu/usr.bin/gcc/gcc/cp/
H A Dtypeck.c4136 tree incremented, modify, value, compound; local
4150 compound = build (COMPOUND_EXPR, TREE_TYPE (arg), modify, value);
4153 TREE_NO_UNUSED_WARNING (compound) = 1;
4154 return compound;

12345