Lines Matching refs:conflict

836 The present example contains only one conflict between two
837 rules, and the type-declaration context containing the conflict
884 about one reduce/reduce conflict.  In the conflicting situation the
894 to be silent about the one known reduce/reduce conflict, by
916 conflict.  Second, consider interactions with the lexer (@pxref{Semantic
997 Bison detects this as a reduce/reduce conflict between the rules
1001 each choice of resolving the reduce/reduce conflict.
1033 have enough information to resolve the reduce/reduce conflict (again,
3716 all token types.  Bison will automatically select codes that don't conflict
3991 @cindex suppressing conflict warnings
4047 Now Bison will warn you if you introduce an unexpected conflict, but
4328 language with the same program?  Then you need to avoid a name conflict
4335 names that do not conflict.
4343 renamed.} These others are not global; there is no conflict if the same
5214 called a @dfn{shift/reduce conflict}.  Bison is designed to resolve
5239 The conflict exists because the grammar as written is ambiguous: either
5254 conflict, but the conflict does not actually appear without additional
5256 conflict:
5407 (@pxref{Invocation, ,Invoking Bison}) says how each conflict was
5483 for all rules that participate in precedence conflict resolution.
5484 Then you will see any shift/reduce conflict until you tell Bison how
5521 @cindex reduce/reduce conflict
5524 A reduce/reduce conflict occurs if there are two or more rules that apply
5564 Bison resolves a reduce/reduce conflict by choosing to use the rule that
5566 reduce/reduce conflict must be studied and usually eliminated.  Here is the
5577 Here is another common error that yields a reduce/reduce conflict:
5689 the two contexts causes a conflict later.  In parser terminology, this
5777 differently in cases where there is a shift-reduce conflict that has not
5779 reduce-reduce conflict.  When a @acronym{GLR} parser encounters such a
6536 conflict means that either the grammar is ambiguous, or the parser lacks
8248 reduce/reduce conflict with a rule having the same merging function, the