-
Notifications
You must be signed in to change notification settings - Fork 85
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
Update Rust to 1.75.0 #87
Conversation
de8fc12
to
c556713
Compare
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.
Does this point to the latest pushed commit on branch solana-rustc/17.0-2023-12-14? 741642838f9c1df60956a0d2fd9810d5638dddba
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.
Thanks for noticing this. It was point to my fork until we merged anza-xyz/llvm-project#85. Now that it is merged, I need to update the llvm commit in this PR.
Fix `is_from_proc_macro` patterns fixes rust-lang#11533 changelog: none
[`unused_enumerate_index`]: don't ICE on empty tuples Fixes rust-lang#11755 changelog: [`unused_enumerate_index`]: don't ICE on empty tuples I'm going to nominate for beta backport because the code that is needed to trigger this seems likely to occur in real code `@rustbot` label +beta-nominated
Don't check for late-bound vars, check for escaping bound vars Fixes an assertion that didn't make sense. Many valid and well-formed types *have* late-bound vars (e.g. `for<'a> fn(&'a ())`), they just must not have *escaping* late-bound vars in order to be normalized correctly. Addresses rust-lang/rust-clippy#11230, cc `@jyn514` and `@matthiaskrgr` changelog: don't check for late-bound vars, check for escaping bound vars. Addresses rust-lang/rust-clippy#11230
Fix binder handling in `unnecessary_to_owned` fixes rust-lang#11952 The use of `rebind` instead of `EarlyBinder::bind` isn't technically needed, but it is the semantically correct operation. changelog: None
With this _RELATIVE relocations can be ignored in the vm. Relocations are still produced in case we change address space layout in the future.
sbfv2 only produces _RELATIVE relocations and those can be packed much more efficiently using SHT_RELR. See https://reviews.llvm.org/D48247.
Make a solana specific version of __rdl_oom handler that doesn't use a static variable. This variable can't be supported is Solana execution environment.
c556713
to
933bd94
Compare
No description provided.