Lines Matching full:conflicts
215 * Mid-Rule Conflicts:: Mid-rule actions can cause conflicts.
233 * Expect Decl:: Suppressing warnings about parsing conflicts.
269 * Shift/Reduce:: Conflicts: when either shifting or reduction is valid.
270 * Precedence:: Operator precedence works by resolving conflicts.
274 * Mysterious Conflicts:: Conflicts that look unjustified.
285 * Non Operators:: Using precedence for general conflicts.
513 @xref{Mysterious Conflicts}, for more information on this. As an
735 @cindex conflicts
736 @cindex shift/reduce conflicts
737 @cindex reduce/reduce conflicts
745 input. These are known respectively as @dfn{reduce/reduce} conflicts
746 (@pxref{Reduce/Reduce}), and @dfn{shift/reduce} conflicts
754 contain no unresolved conflicts
756 faced with unresolved shift/reduce and reduce/reduce conflicts,
792 @cindex conflicts
793 @cindex reduce/reduce conflicts
794 @cindex shift/reduce conflicts
960 analyze the conflicts reported by Bison to make sure that GLR
985 @cindex conflicts
986 @cindex reduce/reduce conflicts
3751 * Mid-Rule Conflicts:: Mid-rule actions can cause conflicts.
3949 @node Mid-Rule Conflicts
3950 @subsubsection Conflicts due to Mid-Rule Actions
3952 conflicts since the parser must commit to a parse in order to execute the
4381 * Expect Decl:: Suppressing warnings about parsing conflicts.
4905 @cindex preventing warnings about conflicts
4907 @cindex conflicts, suppressing warnings of
4911 Bison normally warns if there are any conflicts in the grammar
4912 (@pxref{Shift/Reduce, ,Shift/Reduce Conflicts}), but most real grammars
4913 have harmless shift/reduce conflicts which are resolved in a predictable
4915 the warning about these conflicts unless the number of conflicts
4925 be @var{n} shift/reduce conflicts and no reduce/reduce conflicts.
4926 Bison reports an error if the number of shift/reduce conflicts differs
4927 from @var{n}, or if there are any reduce/reduce conflicts.
4929 For deterministic parsers, reduce/reduce conflicts are more
4931 reduce/reduce conflicts for these parsers. With GLR
4932 parsers, however, both kinds of conflicts are routine; otherwise,
4934 also possible to specify an expected number of reduce/reduce conflicts
4946 to get a verbose list of where the conflicts occur. Bison will also
4947 print the number of conflicts.
4950 Check each of the conflicts to make sure that Bison's default
5181 Declare the expected number of shift-reduce conflicts
5783 with the same program? Then you need to avoid name conflicts between
5786 also need to avoid conflicts on types and macros (e.g., @code{YYSTYPE})
6676 * Shift/Reduce:: Conflicts: when either shifting or reduction is valid.
6677 * Precedence:: Operator precedence works by resolving conflicts.
6681 * Mysterious Conflicts:: Conflicts that look unjustified.
6749 @section Shift/Reduce Conflicts
6750 @cindex conflicts
6751 @cindex shift/reduce conflicts
6779 these conflicts by choosing to shift, unless otherwise directed by
6813 conflicts, you can use the @code{%expect @var{n}} declaration.
6814 There will be no warning as long as the number of shift/reduce conflicts
6819 number of conflicts does not mean that they are the @emph{same}. When
6821 conflicts explicitly (@pxref{Non Operators,, Using Precedence For Non
6857 Another situation where shift/reduce conflicts appear is in arithmetic
6867 * Non Operators:: Using precedence for general conflicts.
6970 Finally, the resolution of conflicts works by comparing the precedence
6986 shift/reduce conflicts that do not involve arithmetics-like operators. For
6988 Shift/Reduce Conflicts}) can be solved elegantly in two different ways.
7015 Therefore, instead of being warned about new conflicts you would be unaware
7052 altered rule precedence then affects how conflicts involving that rule
7128 @section Reduce/Reduce Conflicts
7130 @cindex conflicts, reduce/reduce
7316 @node Mysterious Conflicts
7317 @section Mysterious Conflicts
7318 @cindex Mysterious Conflicts
7320 Sometimes reduce/reduce conflicts can occur that don't look warranted.
7375 mysterious reduce/reduce conflicts. The best way to fix all these problems
7432 the previous section, we discussed the mysterious conflicts that can be
7465 Conflicts}.
7499 @noindent For the example in @ref{Mysterious Conflicts}, the mysterious
7526 conflicts statically (for example, with @code{%left} or @code{%prec}), then
7531 Nevertheless, once you begin to resolve conflicts statically, GLR behaves
7533 conflicts appear, and so either IELR or canonical LR can then be helpful to
7553 duplicate conflicts in the case of non-LR grammars, the number of conflicts
7813 Unreachable states may contain conflicts and may use rules not used in any
7848 Finally, as previously mentioned (@pxref{Mysterious Conflicts}),
7863 tokens in lock-step. Some of the stacks may encounter other conflicts
8380 calc.y: conflicts: 7 shift/reduce
8412 The next section lists states that still have conflicts.
8415 State 8 conflicts: 1 shift/reduce
8416 State 9 conflicts: 1 shift/reduce
8417 State 10 conflicts: 1 shift/reduce
8418 State 11 conflicts: 4 shift/reduce
8614 As was announced in beginning of the report, @samp{State 8 conflicts:
8644 Shift/Reduce Conflicts}. Discarded actions are reported between
8677 the conflicts on @samp{/}), @samp{NUM + NUM * NUM} is not: the conflict was
8680 conflicts in the report:
8746 Observe that state 11 contains conflicts not only due to the lack of
8859 When unresolved conflicts are present, because in deterministic parsing
8861 reduction, see @ref{Shift/Reduce, , Shift/Reduce Conflicts}. Discarded actions
9361 @item conflicts-sr
9362 @itemx conflicts-rr
9363 S/R and R/R conflicts. These warnings are enabled by default. However, if
9365 unexpected number of conflicts is an error, and an expected number of
9366 conflicts is not reported, so @option{-W} and @option{--warning} then have
9550 Description of the grammar, conflicts (resolved and unresolved), and
9562 Implies @code{state}. Explain how conflicts were solved thanks to
11354 These tokens prevents the introduction of new conflicts. As far as the
11650 time to resolve reduce/reduce conflicts. @xref{GLR Parsers, ,Writing
12110 extra parser states may contain duplicate conflicts in the case of non-LR(1)
12111 grammars, the number of conflicts for IELR(1) is often an order of magnitude
12167 @xref{Mysterious Conflicts}.
