Fabian Ruffy
Fabian Ruffy
> @fruffy I have made the requested changes. Can you review it again. Let me take a look later this week.
Possible related: https://github.com/p4lang/p4c/issues/43? More funky behavior by the IR::IndexVector class.
Related IR::IndexVector issues: https://github.com/p4lang/p4c/issues/4117 https://github.com/p4lang/p4c/issues/43 One of the oldest issues still open.
Encoding pre- and postconditions in the compiler passes to understand what they require or produce has been a longstanding goal iirc. (cc'ing @jnfoster). The problem is just the effort it...
Hi @icycodes, any updates on this problem? How easy is it to fix?
Looks like a racecondition to me. Not quite clear why the Python lex/yacc code is sharing state here.
What about https://github.com/p4lang/p4c/issues/4385?
> See [#4797 (comment)](https://github.com/p4lang/p4c/pull/4797#issue-2406024872).. Mihai's PRs masked the root problem, so I do not know of any test cases that pass with this PR but not on `main` branch. This...
At least according to the specification this seems valid to me? https://p4.org/p4-spec/docs/P4-16-working-spec.html#sec-set-exprs A `default` is equivalent to `_`. This duplication appears like an oversight to me, however.
There was a pass in the works to remove or simplify overlapping matches but it was never finished: https://github.com/p4lang/p4c/pull/2591