Lines Matching full:conflicts
178 * Mid-Rule Conflicts:: Mid-rule actions can cause conflicts.
196 * Expect Decl:: Suppressing warnings about parsing conflicts.
232 * Shift/Reduce:: Conflicts: when either shifting or reduction is valid.
233 * Precedence:: Operator precedence works by resolving conflicts.
237 * Mysterious Conflicts:: Conflicts that look unjustified.
248 * Non Operators:: Using precedence for general conflicts.
1194 Conflicts::, for more information on this. As an experimental feature,
1405 "reduce/reduce" conflicts (*note Reduce/Reduce::), and "shift/reduce"
1406 conflicts (*note Shift/Reduce::).
1412 handle Bison grammars that contain no unresolved conflicts (i.e., after
1415 conflicts, GLR parsers use the simple expedient of doing both,
1580 the conflicts reported by Bison to make sure that GLR splitting is only
3996 * Mid-Rule Conflicts:: Mid-rule actions can cause conflicts.
4109 File: bison.info, Node: Mid-Rule Action Translation, Next: Mid-Rule Conflicts, Prev: Using Mid-Rule Actions, Up: Mid-Rule Actions
4160 File: bison.info, Node: Mid-Rule Conflicts, Prev: Mid-Rule Action Translation, Up: Mid-Rule Actions
4162 3.5.5.3 Conflicts due to Mid-Rule Actions
4166 conflicts since the parser must commit to a parse in order to execute
4516 * Expect Decl:: Suppressing warnings about parsing conflicts.
4937 Bison normally warns if there are any conflicts in the grammar (*note
4938 Shift/Reduce Conflicts: Shift/Reduce.), but most real grammars have
4939 harmless shift/reduce conflicts which are resolved in a predictable way
4941 warning about these conflicts unless the number of conflicts changes.
4949 shift/reduce conflicts and no reduce/reduce conflicts. Bison reports
4950 an error if the number of shift/reduce conflicts differs from N, or if
4951 there are any reduce/reduce conflicts.
4953 For deterministic parsers, reduce/reduce conflicts are more serious,
4955 reduce/reduce conflicts for these parsers. With GLR parsers, however,
4956 both kinds of conflicts are routine; otherwise, there would be no need
4958 expected number of reduce/reduce conflicts in GLR parsers, using the
4966 get a verbose list of where the conflicts occur. Bison will also
4967 print the number of conflicts.
4969 * Check each of the conflicts to make sure that Bison's default
5169 Declare the expected number of shift-reduce conflicts (*note
5666 conflicts between different definitions of functions and variables such
5668 compilation unit, you also need to avoid conflicts on types and macros
6410 * Shift/Reduce:: Conflicts: when either shifting or reduction is valid.
6411 * Precedence:: Operator precedence works by resolving conflicts.
6415 * Mysterious Conflicts:: Conflicts that look unjustified.
6477 5.2 Shift/Reduce Conflicts
6499 these conflicts by choosing to shift, unless otherwise directed by
6530 shift/reduce conflicts, you can use the `%expect N' declaration. There
6531 will be no warning as long as the number of shift/reduce conflicts is
6535 number of conflicts does not mean that they are the _same_. When
6537 conflicts explicitly (*note Using Precedence For Non Operators: Non
6566 Another situation where shift/reduce conflicts appear is in arithmetic
6577 * Non Operators:: Using precedence for general conflicts.
6674 Finally, the resolution of conflicts works by comparing the
6693 shift/reduce conflicts that do not involve arithmetics-like operators.
6695 Conflicts: Shift/Reduce.) can be solved elegantly in two different ways.
6716 grammar. Therefore, instead of being warned about new conflicts you
6749 altered rule precedence then affects how conflicts involving that rule
6797 File: bison.info, Node: Reduce/Reduce, Next: Mysterious Conflicts, Prev: Parser States, Up: Algorithm
6799 5.6 Reduce/Reduce Conflicts
6947 File: bison.info, Node: Mysterious Conflicts, Next: Tuning LR, Prev: Reduce/Reduce, Up: Algorithm
6949 5.7 Mysterious Conflicts
6952 Sometimes reduce/reduce conflicts can occur that don't look warranted.
6991 beyond just mysterious reduce/reduce conflicts. The best way to fix
7039 File: bison.info, Node: Tuning LR, Next: Generalized LR Parsing, Prev: Mysterious Conflicts, Up: Algorithm
7046 example, in the previous section, we discussed the mysterious conflicts
7079 this effect in *note Mysterious Conflicts::.
7110 For the example in *note Mysterious Conflicts::, the mysterious
7135 not resolve any conflicts statically (for example, with
7142 resolve conflicts statically, GLR behaves more like a
7144 conflicts appear, and so either IELR or canonical LR can then
7165 duplicate conflicts in the case of non-LR grammars, the number of
7166 conflicts for IELR is often an order of magnitude less as well.
7419 Unreachable states may contain conflicts and may use rules not
7453 Finally, as previously mentioned (*note Mysterious Conflicts::), there
7466 tokens in lock-step. Some of the stacks may encounter other conflicts
7944 calc.y: conflicts: 7 shift/reduce
7966 The next section lists states that still have conflicts.
7968 State 8 conflicts: 1 shift/reduce
7969 State 9 conflicts: 1 shift/reduce
7970 State 10 conflicts: 1 shift/reduce
7971 State 11 conflicts: 4 shift/reduce
8129 As was announced in beginning of the report, `State 8 conflicts: 1
8157 Conflicts: Shift/Reduce. Discarded actions are reported between square
8188 results in the conflicts on `/'), `NUM + NUM * NUM' is not: the
8191 solved conflicts in the report:
8245 Observe that state 11 contains conflicts not only due to the lack of
8367 When unresolved conflicts are present, because in deterministic parsing
8369 reduction, see *note Shift/Reduce Conflicts: Shift/Reduce. Discarded
8814 `conflicts-sr'
8815 `conflicts-rr'
8816 S/R and R/R conflicts. These warnings are enabled by
8818 is specified, an unexpected number of conflicts is an error,
8819 and an expected number of conflicts is not reported, so `-W'
8976 Description of the grammar, conflicts (resolved and
8989 Implies `state'. Explain how conflicts were solved thanks to
10553 These tokens prevents the introduction of new conflicts. As far as
10820 parse time to resolve reduce/reduce conflicts. *Note Writing GLR
11215 contain duplicate conflicts in the case of non-LR(1) grammars, the
11216 number of conflicts for IELR(1) is often an order of magnitude
11274 *Note Mysterious Conflicts::.
12192 * canonical LR <1>: Mysterious Conflicts.
12202 * conflicts <1>: Merging GLR Parses. (line 6)
12203 * conflicts <2>: Shift/Reduce. (line 6)
12204 * conflicts <3>: GLR Parsers. (line 6)
12205 * conflicts: Simple GLR Parsers. (line 6)
12206 * conflicts, reduce/reduce: Reduce/Reduce. (line 6)
12207 * conflicts, suppressing warnings of: Expect Decl. (line 6)
12338 * IELR: Mysterious Conflicts.
12361 * LALR: Mysterious Conflicts.
12394 * LR: Mysterious Conflicts.
12411 * Mysterious Conflicts: Mysterious Conflicts.
12458 * preventing warnings about conflicts: Expect Decl. (line 6)
12474 * reduce/reduce conflicts <1>: Simple GLR Parsers. (line 6)
12475 * reduce/reduce conflicts <2>: GLR Parsers. (line 6)
12476 * reduce/reduce conflicts: Merging GLR Parses. (line 6)
12501 * shift/reduce conflicts <1>: Simple GLR Parsers. (line 6)
12502 * shift/reduce conflicts <2>: GLR Parsers. (line 6)
12503 * shift/reduce conflicts: Shift/Reduce. (line 6)
12733 Node: Mid-Rule Conflicts172475
12782 Node: Mysterious Conflicts281576
