Lines Matching full:conflicts
115 The sections about shift/reduce and reduce/reduce conflicts resolution
517 conflicts in the case of non-LR(1) grammars, the number of conflicts
746 that would actually induce a syntax error because conflicts for them
782 *** Bison now treats S/R and R/R conflicts like other warnings:
786 "conflicts-sr" and "conflicts-rr". This change has important
790 bison -Wno-conflicts-sr gram.y # S/R conflicts not reported
791 bison -Wno-conflicts-rr gram.y # R/R conflicts not reported
792 bison -Wnone gram.y # no conflicts are reported
796 specified, an unexpected number of conflicts is an error, and an
797 expected number of conflicts is not reported, so -W and --warning
829 grammar rules that are useless in the parser due to conflicts.
1056 2. Does not report any conflicts that appeared in unreachable states.
1061 "useless in parser due to conflicts".
1339 Incorrect numbers of expected conflicts are now actual errors,
1432 reduce/reduce conflicts in GLR parsers.
1449 reduce/reduce conflicts) and with Bison 1.30 and earlier (when there
1450 are too many or too few shift/reduce conflicts). However, in future
1526 "conflicts: 2 shift/reduce, 1 reduce/reduce".
1684 Rules that can never be reduced because of conflicts are now
1741 describe shift/reduce conflicts solving.
1743 the report. Solved conflicts are now attached to their states.
1819 GNU Gettext asserts 10 s/r conflicts, but there are 7. Now that
1855 When the number of shift/reduce conflicts is correct, don't issue
1875 Some conflicts in state descriptions were missing.
