Bug 19056
| Summary: | yacc in 3.4 and 4.0 reports "maximum table size exceeded" | ||
|---|---|---|---|
| Product: | Base System | Reporter: | gryphon <gryphon> |
| Component: | bin | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
State Changed From-To: open->feedback Need more details about actual grammar. GNATSe the reason for changing this PR's status here. State Changed From-To: feedback->closed Automatic feedback timeout. If additional feedback that warrants the re-opening of this PR is available but not included in the audit trail, please include the feedback in a reply to this message (preserving the Subject line) and ask that the PR be re-opened. |
When using yacc on either platform, a specific grammer results in the fatal error "maximum table size exceeded". However, according ORA's book on Yacc, this usually indicates a bug in the yacc program. In this case, the grammer only has: 340 terminals, 200 nonterminals 615 grammar rules, 920 states Which is actually significantly less non-terminals, rules and states than it had when the problem first showed up. I am using bison (1.28) as countercheck and it works fine. How-To-Repeat: Anything the yacc program is run with the current language grammar. Unfortunately, I wasn't able to isolate the grammar change that caused the initial overflow, and developement has had to proceed since then. If absolutely necessary, I can make the grammar that causes the problem available under an NDA for testing purposes.