fix for ZAM optimization of assigning a record field to result of "in" operation

This commit is contained in:
Vern Paxson 2024-12-17 19:49:43 -08:00
parent f940f2d88f
commit 6e549554b8
3 changed files with 25 additions and 1 deletions

View file

@ -176,7 +176,6 @@ bool Expr::IsFieldAssignable(const Expr* e) const {
case EXPR_RSHIFT:
case EXPR_FIELD:
case EXPR_HAS_FIELD:
case EXPR_IN:
case EXPR_SIZE:
return true;
@ -189,6 +188,8 @@ bool Expr::IsFieldAssignable(const Expr* e) const {
// case EXPR_NE:
// case EXPR_GE:
// case EXPR_GT:
//
// case EXPR_IN:
// These could be added if we subsetted them to versions for
// which we know it's safe to evaluate both operands. Again