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
Hi! When compiling the program below with --via-ir --optimize and using --optimize-runs 200 and --optimize-runs 99999999 respectively, different error codes are returned when the f() function is called. Specifically, --optimize-runs 200 yields 0x4e487b710000000000000000000000000000000000000000000000000000000000000032, while --optimize-runs 99999999 results in 0x0. I conducted tests on Remix using the 0.8.27 compiler version, and the issue can be reproduced on the latest compiler version as well.
I'm interested in knowing: are error codes always accurate, and what is the correct error code?
Here's another example: at a lower optimization level (200), executing the transaction f() results in an error code of 0x32. However, at a higher optimization level (99999999), the transaction successfully returns.
Hi! When compiling the program below with
--via-ir --optimize
and using--optimize-runs 200
and--optimize-runs 99999999
respectively, different error codes are returned when thef()
function is called. Specifically,--optimize-runs 200
yields0x4e487b710000000000000000000000000000000000000000000000000000000000000032
, while--optimize-runs 99999999
results in0x0
. I conducted tests on Remix using the0.8.27
compiler version, and the issue can be reproduced on the latest compiler version as well.I'm interested in knowing: are error codes always accurate, and what is the correct error code?
The text was updated successfully, but these errors were encountered: