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
I think this code is necessary because it checks to see if the index specified by insertelement is in an accessible range on the vector, so I think we need to add exception handling to fix the problem.
What do you think?
Note that this is not a real-world issue, but a bug that I discovered while writing the patch and creating the verification code.
The text was updated successfully, but these errors were encountered:
No. I am trying to verify i8 type for that IR because I was trying to support multiple inserts but alive didn't make it. So i reduce type size then occured this issue.
I'm not sure whether this should be addressed or not - oddly the langref doesn't say that the index type must be able to dereference all elements, just that its treated as unsigned (so I guess we assume implicit zext?)
This is an IR sample that crashes.
and this is debugging message with crash dump
problem occured here
I think this code is necessary because it checks to see if the index specified by insertelement is in an accessible range on the vector, so I think we need to add exception handling to fix the problem.
What do you think?
Note that this is not a real-world issue, but a bug that I discovered while writing the patch and creating the verification code.
The text was updated successfully, but these errors were encountered: