-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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 change during 0.6 development cycle #21305
Comments
Yes, I've seen this too. Something regressed in inference's ability to constant fold type parameters. |
Although I'm not done the bisect yet, tentatively 8fee77f is the most likely cause (#20726). The symptoms match up in this particular case. While there is no actual risk of a |
Yep, the bisect confirms that
|
Fixed by #21310. |
fix #21305, inference of splatting T.types or T.parameters
The output of this file
is on 0.5, quite long; on latest 0.6, also quite long.
But briefly, around when #16961 was merged, it was just
so something must have changed since. (The latest commit I know to have the short LLVM is 495114c, but I'll bisect to find a better bound.)
cc @JeffBezanson
Some notes:
@pure
is removed then the generated LLVM is never short;@pure
is incorrect anyway, so we should probably still go with Refactor null_safe_op to workaround codegen changes #21290?The text was updated successfully, but these errors were encountered: