-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Rollup of 11 pull requests #100847
Rollup of 11 pull requests #100847
Conversation
Simple Clamp Function I thought this was more robust and easier to read. I also allowed this function to return early in order to skip the extra bound check (I'm sure the difference is negligible). I'm not sure if there was a reason for binding `self` to `x`; if so, please correct me. Simple Clamp Function for f64 I thought this was more robust and easier to read. I also allowed this function to return early in order to skip the extra bound check (I'm sure the difference is negligible). I'm not sure if there was a reason for binding `self` to `x`; if so, please correct me. Floating point clamp test f32 clamp using mut self f64 clamp using mut self Update library/core/src/num/f32.rs Update f64.rs Update x86_64-floating-point-clamp.rs Update src/test/assembly/x86_64-floating-point-clamp.rs Update x86_64-floating-point-clamp.rs Co-Authored-By: scottmcm <scottmcm@users.noreply.github.com>
Co-authored-by: scottmcm <scottmcm@users.noreply.github.com>
LLVM commit llvm/llvm-project@c2a3888 updates the PIC level version selection. This updates the rust tests to work under both the old and new behaviors. Detected by our experimental rust + llvm @ HEAD bot: https://buildkite.com/llvm-project/rust-llvm-integrate-prototype/builds/12829#0182b368-a405-47a2-b3da-9c79cb907bfe/701-709
The comment is on find_vtable_types_for_unsizing, but there is another unrelated typo fix as well.
To avoid rust-analyzer and rustc having to wait for each other, the dev guide mentions using another build directory for RA. We should also put this into the .gitignore, just like the normal `build`.
The other fields use this format and example.
Module is complete because it has zero diagnostics.
Clamp Function for f32 and f64 I thought the clamp function could use a little improvement for readability purposes. The function now returns early in order to skip the extra bound checks. If there was a reason for binding `self` to `x` or if this code is incorrect, please correct me :)
Make slice::reverse const I remember this not being doable for some reason before, but decided to try it again and everything worked out in the tests.
…er-errors Minor syntax and formatting update to doc comment on `find_vtable_types_for_unsizing` I noticed the code examples on this function weren't formatted as code, and also the that the syntax for trait objects was out of date (or just incorrect). This should bring it up to date.
update test for LLVM change LLVM commit llvm/llvm-project@c2a3888 updates the PIC level version selection. Updated an affected rust test to work under both the old and new behaviors. Detected by our experimental rust + llvm @ HEAD bot: https://buildkite.com/llvm-project/rust-llvm-integrate-prototype/builds/12829#0182b368-a405-47a2-b3da-9c79cb907bfe/701-709
…r-errors some general mir typeck cleanup this pr contains the parts of rust-lang#95763 which already work correctly. the remaining commits of that PR have some issues which are more complex to fix. r? types
…otriddle rustdoc: Merge source code pages HTML elements together v2 This is the follow-up of rust-lang#100429. I strongly recommend to review it one commit at a time because otherwise it's a lot at once. For these ones, on each page, I run this JS: `document.getElementsByTagName('*').length`. The goal is to count the number of DOM elements. I took some pages that seemed big, but don't hesitate to check some others. I also added the "starting point" because it's quite nice to see how much the page was reduced thanks to these two PRs. | file name | before rust-lang#100429 | before this PR | with this PR | diff | |-|-|-|-|-| | std/lib.rs.html (source link on std crate page) | 3455 | 2332 | 1772 | 24% | | alloc/vec/mod.rs.html (source on Vec type page) | 11012 | 5982 | 5833 | 2.5% | | alloc/string.rs.html (source on String type page) | 10800 | 6010 | 5822 | 3.2% | | std/sync/mutex.rs.html (source on Mutex type page) | 2953 | 2041 | 2038 | 0.1% | So unsurprisingly, the more attributes you have, the bigger the difference. You can test it [here](https://rustdoc.crud.net/imperio/reduce-span-v2/src/std/lib.rs.html). cc ``````@jsha`````` r? ``````@notriddle``````
…gnore, r=Mark-Simulacrum Add `/build-rust-analyzer/` to .gitignore To avoid rust-analyzer and rustc having to wait for each other, the [dev guide](https://rustc-dev-guide.rust-lang.org/building/suggested.html#configuring-rust-analyzer-for-rustc) mentions using another build directory for RA. We should also put this into the .gitignore, just like the normal `build`.
Make some docs nicer wrt pointer offsets This PR replaces `pointer::offset` with `pointer::add` and similarly `.cast().wrapping_add().cast()` with `.wrapping_byte_add()` **in docs**. r? ``````@scottmcm`````` _split off from #100746_
…rk, r=scottmcm Replace most uses of `pointer::offset` with `add` and `sub` As PR title says, it replaces `pointer::offset` in compiler and standard library with `pointer::add` and `pointer::sub`. This generally makes code cleaner, easier to grasp and removes (or, well, hides) integer casts. This is generally trivially correct, `.offset(-constant)` is just `.sub(constant)`, `.offset(usized as isize)` is just `.add(usized)`, etc. However in some cases we need to be careful with signs of things. r? ````@scottmcm```` _split off from #100746_
…_field_desc, r=thomcc Make doc for stdin field of process consistent The other fields use this format and example.
@bors r+ rollup=never p=10 |
⌛ Testing commit 5ba68df with merge 11d4ec375309a84976ab817f5a2a9537cbb53aba... |
💔 Test failed - checks-actions |
😭 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR: In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (c0941df): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Footnotes |
Not sure why this was tagged as a regression when there was just a single relevant instruction count regression of 0.20%. @rustbot label: +perf-regression-triaged |
@nnethercote the reason this was marked as a regression is because it was considered a mix result (both regressions and improvements). Whether a run is considered mixed vs just an improvement/regression is based on percentages. I believe this is the relevant calculation. |
Successful merges:
find_vtable_types_for_unsizing
#100697 ( Minor syntax and formatting update to doc comment onfind_vtable_types_for_unsizing
)/build-rust-analyzer/
to .gitignore #100813 (Add/build-rust-analyzer/
to .gitignore)pointer::offset
withadd
andsub
#100822 (Replace most uses ofpointer::offset
withadd
andsub
)rustc_transmute
module (zero diags) #100842 (Add diagnostics lints torustc_transmute
module (zero diags))Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup