Kyle Cripps

Compiler Bug: Overwriting definitions at <MethodCallExpression>(22038)//<MethodCallExpression>(22017)//<BoolLiteral>(1718)

5

Compiling the following P4 code: ``` extern void __e(in bit arg); extern void __e2(in bit arg); control C() { action bar(bool a, bool b) { bit x; bit y; if...

Compiler Bug: Expression E write set already set

4

Compiling the following P4 code: ``` enum E { e0 } extern void bar(E x); extern void baz(); void foo(E y) { bar(y); if (y == E.e0) baz(); } control...

"Could not infer a type for parameter..." error should be removed

7

I am curious why the source code at testdata/p4_16_errors_outputs/methodArgDontcare.p4 is not expected to compile. In my opinion, [this error](https://github.com/p4lang/p4c/commit/facc5ed5ac5d223b55c6d1dede5373493c41eab9#diff-addc7332865e8036bf6b0c6299bcc2a5ef895596dcfb1e7e5fb44c0fefcd488eR3601) should not have been added by #3901 (#3808 was actually fixed...

Clarify expected behavior of `--W*=diagnostic` option when `diagnostic` can be an error

18

Some warnings and errors have the same name, for example `ERR_INVALID` and `WARN_INVALID`: ``` // map from errorCode to ErrorSig std::map ErrorCatalog::errorCatalog = { // Errors {ErrorType::LEGACY_ERROR, "legacy"}, {ErrorType::ERR_UNKNOWN, "unknown"},...

[#4656] Explicitly delay constant folding of only action enum `IR::SwitchCase` `label` expressions, instead of delaying constant folding of all `IR::Mux` expressions

14

This is one possible fix for #4656. For example, one possible alternative might be to revert https://github.com/p4lang/p4c/pull/3633 and add a check for action enum `SwitchStatement` labels, similar to the one...

Compiling ``` #include extern void foo(); extern void bar(); extern bit baz(); action a(){} action b(){} control c() { table t { actions = { a ; b; } }...

[#4656] Revert PR #3633 so that mux expressions will be constant folded

3

Reverts https://github.com/p4lang/p4c/commit/4a74084c675a3e8bdf7a318e468cbd5bb27c6914, as discussed as an alternate fix for #4656 in https://github.com/p4lang/p4c/pull/4657.

With 01fedcc0ee74b39e6e23aa7217b4080fcd22d4a6, compiling the following P4 program: ``` header h_t { bit f; } control C() { action bar() { } table t { actions = { bar; } default_action...

`p4c` should prohibit different controllable entities having the same control-plane name

10

For example: ``` header h_t { bit f; } control C() { @name(".act") action bar() {} @name(".act") action foo() {} table t { actions = { bar; } default_action =...