-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
Remove all ConstPropNonsense #119627
The head ref may contain hidden characters: "const_prop_lint_n\u0335o\u0335n\u0335sense"
Remove all ConstPropNonsense #119627
Changes from all commits
fbd10a3
ac48ad5
e904a64
0294a0d
89e6a67
6ecb2aa
1f398ab
249ec9f
3419273
2d99ea0
d03eb33
6a01dc9
c5e371d
271821f
1c9e621
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. CanConstProp is only used by const_prop_lint, so IMO it makes more sense to move it over there. Then this file can be removed. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I was thinking of making this file a support for the other passes that use an interpreter:
And eventually common code like arithmetic identities. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That also works, but then it should be called something like |
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.
Given that this is causing ICEs and needs extra work-arounds in dataflow-const-prop, I wonder if the more pragmatic choice wouldn't be to just remove the assertion.