Searched refs:ambiguity (Results 1 – 25 of 32) sorted by relevance
12
2 header "Inputs/macro-ambiguity/a/quote/a_quote.h"3 header "Inputs/macro-ambiguity/a/system/a_system.h"7 header "Inputs/macro-ambiguity/b/quote/b_quote.h"8 header "Inputs/macro-ambiguity/b/system/b_system.h"12 header "Inputs/macro-ambiguity/c/quote/c_quote.h"13 header "Inputs/macro-ambiguity/c/system/c_system.h"17 header "Inputs/macro-ambiguity/d/quote/d_quote.h"18 header "Inputs/macro-ambiguity/d/system/d_system.h"22 textual header "Inputs/macro-ambiguity/e/quote/e_quote.h"23 textual header "Inputs/macro-ambiguity/e/system/e_system.h"
394 AT_SETUP([GLR: Resolve ambiguity, impure, no locations])401 AT_SETUP([GLR: Resolve ambiguity, impure, locations])407 AT_SETUP([GLR: Resolve ambiguity, pure, no locations])414 AT_SETUP([GLR: Resolve ambiguity, pure, locations])448 AT_SETUP([GLR: Verbose messages, resolve ambiguity, impure, no locations])
1402 ## Leaked semantic values when reporting ambiguity. ##1405 AT_SETUP([Leaked semantic values when reporting ambiguity])1436 parent_rhs_before ambiguity {1449 ambiguity: ambiguity1 | ambiguity2 ;1544 ## Uninitialized location when reporting ambiguity. ##1547 AT_SETUP([Uninitialized location when reporting ambiguity])1569 last position of the ambiguity. */1578 the first position in the ambiguity. */
57 void ambiguity() { in ambiguity() function
72 …[(Class)0 port]; // OK - gcc issues warning but there is only one Class method so no ambiguity to …
110 that extends results to i64, no i32). This solves the ambiguity issue, allows us
94 ambiguity with the words "type" or "class" which have overloaded meanings
70 begin with a number. In case of ambiguity, a token will be interpreted as a
238 * ambiguity, but if one uses appropriately greedy parsing it yields the254 * led to an ambiguity.
35 ambiguity.
478 " with '-a ARCH' to resolve the ambiguity\n",
170 a sample text exhibiting the (LALR) ambiguity. See the paper from
433 * doc/bison.texi (Reduce/Reduce): Fix the resulting ambiguity using2553 * tests/glr-regression.at (Uninitialized location when reporting ambiguity):3586 glr: fix ambiguity reports.
4329 * tests/cxx-type.at (GLR: Resolve ambiguity, pure, no locations):4331 (GLR: Resolve ambiguity, pure, locations): Update.4335 ambiguity): Update8323 ambiguity): Test the above case.8562 (Uninitialized location when reporting ambiguity):8574 ambiguity): New test case.8578 ambiguity.8580 YYLLOC_DEFAULT's usage for ambiguity locations.8586 ambiguity): Remove unnecessary union and type declarations.8596 ambiguity): New test case.[all …]
491 When no ambiguity is possible, original symbol names may be used
127 resolve ambiguity, by querying PTRACE_GETSIGINFO. (Note:
311 which is forbidden to prevent name ambiguity:
199 #. Fix operator= ambiguity on some versions of Clang. (Alex Stewart)
1039 This models a problematic part of the C++ grammar---the ambiguity between1084 Here, there is no ambiguity (this cannot be parsed as a declaration).1097 Suppose that instead of resolving the ambiguity, you wanted to see all1143 @samp{%merge} clauses. Otherwise, the ambiguity would be unresolvable,4193 Before reporting an unresolvable syntactic ambiguity, a GLR4195 of that ambiguity.4205 When a GLR parser reports an ambiguity, which of multiple candidate4310 When ambiguity occurs, explicitly declared names may be used for values and6809 This particular ambiguity was first encountered in the specifications of6810 Algol 60 and is called the ``dangling @code{else}'' ambiguity.[all …]
1653 This models a problematic part of the C++ grammar--the ambiguity between1687 there is no ambiguity (this cannot be parsed as a declaration).1698 Suppose that instead of resolving the ambiguity, you wanted to see1732 ambiguity would be unresolvable, and the parser will report an error4365 reporting an unresolvable syntactic ambiguity, a GLR parser invokes4366 `YYLLOC_DEFAULT' recursively to compute the location of that ambiguity.4376 an ambiguity, which of multiple candidate right hand sides it passes to4458 When ambiguity occurs, explicitly declared names may be used for values6525 hard to do in this case.) This particular ambiguity was first6527 "dangling `else'" ambiguity.[all …]
543 compilation error, due to an ambiguity in name lookup. Therefore, the AST
341 saying enough to avoid any kind of ambiguity?.
845 ambiguity with users named "default".
585 // here because there is no instruction with an ambiguity between ImmSExti64i322859 // effect (both store to a 16-bit mem). Force to sldtw to avoid ambiguity
57 // the given types (or if there is a type ambiguity) an error is