Skip to content

Rollup of 7 pull requests - #101592

Merged
bors merged 15 commits into
rust-lang:masterfrom
compiler-errors:rollup-d2fya7z
Sep 9, 2022
Merged

Rollup of 7 pull requests#101592
bors merged 15 commits into
rust-lang:masterfrom
compiler-errors:rollup-d2fya7z

Conversation

@compiler-errors

Copy link
Copy Markdown
Contributor

Successful merges:

Failed merges:

r? @ghost
@rustbot modify labels: rollup

Create a similar rollup

mkroeningand others added 15 commits September 5, 2022 00:23
No functional changes intended.
Adapts PassWrapper for two recent LLVM API changes:
* llvm/llvm-project@e7bac3b
* llvm/llvm-project@93600eb
* llvm/llvm-project@5e38b2a
This was added in 51f26ac to help with the
display of an `<h3>` tag that has a `<span class='in-band'>` inside.
The way implementation lists were rendered was changed in
34bd2b8 to have `<code class='in-band'>`,
making this CSS unused.
Then it was turned into a `<div>` in 9077d54
without issue.
Finally, the header itself acquired the `in-band` class in
76a3b60.
This was added in 9077d54 to override the
style on `<div>` tags that were acting as headers. These `<div>` tags were
replaced with `<section>` tags in 32f6260,
but this CSS was probably already redundant even then (the headers had
already been replaced with real `<h3>` and `<h4>` tags in
76a3b60).
This CSS was added in 5e01ba3, and served to
override CSS right above it that set a 5px padding for several kinds of
buttons in the same toolbar.
The CSS that it overrode is still there, but now it only applies to
`#settings-menu > a`, so there's nothing to override.
Fix hermit warnings
This fixes two `unused_imprt` and one `dead_code` warning for hermit.
…li-obk
Introduce lowering_arena to avoid creating AST nodes on the fly
`@oli-obk` requested this and other changes as a way of simplifying rust-lang#101345. This is just going to make the diff of rust-lang#101345 smaller.
r? `@oli-obk` `@cjgillot`
llvm-wrapper: adapt for LLVM API changes
No functional changes intended.
Adapts PassWrapper for a few recent LLVM API changes:
* llvm/llvm-project@e7bac3b
* llvm/llvm-project@93600eb
* llvm/llvm-project@5e38b2a
Note that `ModuleMemorySanitizerPass` was renamed back to its pre-14 name, `MemorySanitizerPass`, hence the funky `#if LLVM_VERSION_GE(14, 0) && LLVM_VERSION_LT(16, 0)` guard.
Found via our experimental rust + llvm at HEAD bot: https://buildkite.com/llvm-project/rust-llvm-integrate-prototype/builds/13290#018315e6-24e1-44c8-b56d-9aad9be11c29
…list-h3-span-in-band, r=Dylan-DPC
rustdoc: remove unused CSS `#implementations-list > h3 > span.in-band`
This was added in 51f26ac to help with the display of an `<h3>` tag that has a `<span class='in-band'>` inside.
The way implementation lists were rendered was changed in 34bd2b8 to have `<code class='in-band'>`, making this CSS unused.
Then it was turned into a `<div>` in 9077d54 without issue.
Finally, the header itself acquired the `in-band` class in 76a3b60.
…-div, r=GuillaumeGomez
rustdoc: remove unused CSS `div.impl-items > div`
This was added in 9077d54 to override the style on `<div>` tags that were acting as headers. These `<div>` tags were replaced with `<section>` tags in 32f6260, but this CSS was probably already redundant even then (the headers had already been replaced with real `<h3>` and `<h4>` tags in 76a3b60).
… r=GuillaumeGomez
rustdoc: remove no-op CSS `#settings-menu { padding: 0 }`
This CSS was added in 5e01ba3, and served to override CSS right above it that set a 5px padding for several kinds of buttons in the same toolbar:
https://github.com/rust-lang/rust/blob/5e01ba36c9f1037c4cf3e7421413fc6c41f85d05/src/librustdoc/html/static/css/rustdoc.css#L1400-L1409
The CSS that it overrode is still there, but now it only applies to `#settings-menu > a`, so there's nothing to override.
https://github.com/rust-lang/rust/blob/24d69920201563f0ee7b530f1cda0f171b205cc2/src/librustdoc/html/static/css/rustdoc.css#L1445-L1454
Make `Debug` impl for `Term` useful
because `Term { ptr: 78942378998734298342, maker: PhantomData, }` does not excel at communicating the necessary information
@rustbotrustbot added T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. rollup A PR which is a rollup labels Sep 8, 2022
@compiler-errors

Copy link
Copy Markdown
ContributorAuthor

@bors r+ rollup=never p=7

@bors

bors commented Sep 8, 2022

Copy link
Copy Markdown
Collaborator

📌 Commit e43cf3d has been approved by compiler-errors

It is now in the queue for this repository.

@borsbors added the S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. label Sep 8, 2022
@bors

bors commented Sep 8, 2022

Copy link
Copy Markdown
Collaborator

⌛ Testing commit e43cf3d with merge c6861df...

@bors

bors commented Sep 9, 2022

Copy link
Copy Markdown
Collaborator

☀️ Test successful - checks-actions
Approved by: compiler-errors
Pushing c6861df to master...

@borsbors added the merged-by-bors This PR was explicitly merged by bors. label Sep 9, 2022
@bors
bors merged commit c6861df into rust-lang:masterSep 9, 2022
@rustbotrustbot added this to the 1.65.0 milestone Sep 9, 2022
@rust-timer

Copy link
Copy Markdown
Collaborator

@rust-timer

Copy link
Copy Markdown
Collaborator

Finished benchmarking commit (c6861df): comparison URL.

Overall result: ❌✅ regressions and improvements - ACTION NEEDED

Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please open an issue or create a new PR that fixes the regressions, add a comment linking to the newly created issue or PR, and then add the perf-regression-triaged label to this PR.

@rustbot label: +perf-regression
cc @rust-lang/wg-compiler-performance

Instruction count

This is a highly reliable metric that was used to determine the overall result at the top of this comment.

mean1rangecount2
Regressions ❌
(primary)
--0
Regressions ❌
(secondary)
4.6%[4.6%, 4.6%]1
Improvements ✅
(primary)
-1.2%[-1.3%, -1.1%]2
Improvements ✅
(secondary)
-3.3%[-3.8%, -2.9%]6
All ❌✅ (primary)-1.2%[-1.3%, -1.1%]2

Max RSS (memory usage)

Results

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

mean1rangecount2
Regressions ❌
(primary)
--0
Regressions ❌
(secondary)
0.9%[0.9%, 0.9%]1
Improvements ✅
(primary)
--0
Improvements ✅
(secondary)
-2.2%[-2.2%, -2.2%]1
All ❌✅ (primary)--0

Cycles

Results

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

mean1rangecount2
Regressions ❌
(primary)
--0
Regressions ❌
(secondary)
--0
Improvements ✅
(primary)
--0
Improvements ✅
(secondary)
-2.6%[-3.6%, -2.1%]5
All ❌✅ (primary)--0

Footnotes

  1. the arithmetic mean of the percent change23

  2. number of relevant changes23

@rustbotrustbot added the perf-regression Performance regression. label Sep 9, 2022
@nnethercote

Copy link
Copy Markdown
Contributor

All these changes are just noise.

  • cranelift-codegen and keccak are noisy right now, so those improvements aren't real.
  • The coercions regression is only for a single profile/scenario combination, so I don't think it's meaningful.

@rustbot label: +perf-regression-triaged

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merged-by-borsThis PR was explicitly merged by bors.perf-regressionPerformance regression.perf-regression-triagedThe performance regression has been triaged.rollupA PR which is a rollupS-waiting-on-borsStatus: Waiting on bors to run and complete tests. Bors will change the label on completion.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.T-libsRelevant to the library team, which will review and decide on the PR/issue.T-rustdocRelevant to the rustdoc team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants

@compiler-errors@bors@rust-timer@nnethercote@rustbot@mkroening@krasimirgg@notriddle@spastorino@BoxyUwU