[Bug][compiler-v2] Location information in bytecode verification bugs could be improved #11925
Labels
bug
Something isn't working
compiler-v2
stale-exempt
Prevents issues from being automatically marked and closed as stale
Comments
sausagee
added
the
stale-exempt
|
Closing as fixed by #12534. |
github-project-automation
bot
moved this from 📋 Backlog
to ✅ Done
in Move Language and Runtime
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🐛 Bug
PR #11923 added bytecode verification checks at the end of compilation for compiler v2. If this verification fails due to a bug in the compiler, the location is usually the entire module: it would be nice to have more precise location information.
This issue is slightly hard to reproduce, as you would need to introduce a bug in the compiler to make it fail bytecode verification (an easy way to comment out the ability checks, and run the compiler on code that would have failed ability checks).
Once #11923 lands,
third_party/move/move-compiler-v2/tests/bytecode-verify-failure/equality.expdemonstrates this issue.The text was updated successfully, but these errors were encountered: