[mlir] Add tests for zero-init StringType data area for new bytes(N)

[PavelKopyl]

matter-labs/solx-llvm#84

[Copilot]

Pull request overview

Adds MLIR regression coverage to ensure new bytes(N) allocations are zero-initialized (and that trailing/dirty bytes are masked) when copying dynamic bytes into storage, preventing stale memory/event scratch data from leaking into storage.

Changes:

• Removes the corresponding semantic test from the MLIR semtest failure allowlist.
• Adds an MLIR “print-init” lit test asserting sol.malloc ... zero_init for new bytes(63) (and related setup).
• Adds an EVM “print-std-mlir” lit test capturing the full lowered IR for the three cleanup scenarios (post-event allocation, dirty byte past end, calldata dirty high bits).

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File	Description
test/mlirSemtestFailures.txt	Drops byte_array_to_storage_cleanup from the known-fail list, implying it should now pass under MLIR.
test/lit/mlirCodegen/bytes-to-storage-cleanup.sol	New print-init lit test that checks new bytes(63) uses zero_init in MLIR IR.
test/lit/mlirCodegen/EVM/bytes-to-storage-cleanup.sol	New EVM print-std-mlir lit test exercising storage copy cleanup and masking behavior in the lowered output.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[abinavpp]

thank you!