-
Notifications
You must be signed in to change notification settings - Fork 327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Access Violation on Windows with new PassManager #1078
Comments
What is the target_triple for the system? |
Can you tell me the commands needed to discover that. I looked at: https://llvmlite.readthedocs.io/en/latest/user-guide/binding/target-information.html but then I only got:
|
So I used: And this gave:
|
Thank you that's what I was looking for! Although all 3 reported tests pass for me with this triple, confirming what Graham suggested to me locally that it's probably a false alarm. FYI, this is how I tested it:
|
I can also no longer reproduce this and your sentiment matches mine @yashssh @gmarkall @stuartarchibald. |
It reproduces again. The last couple of llvmlite builds from the buildfarm will reproduce it, e.g.:
However, when I added the PDB to it (#1089), builds that came from that do not reproduce the issue, e.g.:
When I edited the binding init to dump IR after each pass, with:
in
rather than the access violation. At some point there is some invalid IR - perhaps a block is missing a terminator, e.g. as in https://stackoverflow.com/questions/43255774/llvm-what-does-nodeptr-isknownsentinel-function-operator-means. |
Noting that further to the previous comment, setting the |
Also - the access violation occurs during the execution of one of the passes when the |
The text was updated successfully, but these errors were encountered: