You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RemovedUnusedDeclarations will remove unused P4Control, P4Parser, and P4Table objects.
When it removes a P4Table object, it produces a warning with:
if (giveWarning(getOriginal()))
warn(ErrorType::WARN_UNUSED, "Table %1% is not used; removing", table);
But when it removes P4Control/P4Parser objects, it silently removes them without reporting a warning.
Is there a reason why warnings are not reported for P4Control/P4Parser objects? If not, I would like to add similar warnings for those two objet types.
The text was updated successfully, but these errors were encountered:
Add warnings for unused P4Control and P4Parser objects to match P4Table
warnings. Addresses issue #4439.
fruffy
added
bug
This behavior is unintended and should be fixed.
core
Topics concerning the core segments of the compiler (frontend, midend, parser)
labels
Feb 24, 2024
* warn on unused controls/parsers
Add warnings for unused P4Control and P4Parser objects to match P4Table
warnings. Addresses issue #4439.
* remove redundant control/parser
Call externalName() to get the control/parser block name without
"control"/"parser" prepended to the front.
* update expected test output
RemovedUnusedDeclarations will remove unused P4Control, P4Parser, and P4Table objects.
When it removes a P4Table object, it produces a warning with:
But when it removes P4Control/P4Parser objects, it silently removes them without reporting a warning.
Is there a reason why warnings are not reported for P4Control/P4Parser objects? If not, I would like to add similar warnings for those two objet types.
The text was updated successfully, but these errors were encountered: