-
Notifications
You must be signed in to change notification settings - Fork 14.3k
CodeGen: Don't assert when printing null GlobalAddress operands #115531
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
CodeGen: Don't assert when printing null GlobalAddress operands #115531
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm guessing this is for mir files.
I ran into this problem in the past.
LGTM, but could you add a mir test and here add a comment that specifically says that this shouldn't be the state of a well formed ir. (Unless you're fixing a real bug, and then we are missing a test anyway)
I don't think this can be constructed from MIR. A literal 0 won't parse as a GlobalAddress |
So how do you run into this problem? It sounds to me that we shouldn't produce nullptr for GlobalAddress in a normal compilation flow. |
Bugs
Yes, but this is in debug printing. -debug causing new crashes to appear is a bad property |
Fair enough. |
No description provided.