Skip to content

Commit 193e13b

Browse files
KobzolKobzol
authored
Merge pull request #2071 from Kobzol/benchmark-update-2025-cargo
Update cargo to 0.87.1
2 parents 7801fd1 + 1c5c55f commit 193e13b

File tree

1,461 files changed

+344107
-4
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

1,461 files changed

+344107
-4
lines changed

‎.github/workflows/ci.yml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -114,8 +114,8 @@ jobs:
114114
#
115115
# We want the four parts to have similar runtimes.
116116
BENCH_INCLUDE_EXCLUDE_OPTS: [
117-
"--include cargo-0.60.0,stm32f4-0.14.0,webrender-2022",
118-
"--exclude cargo-0.60.0,stm32f4-0.14.0,webrender-2022",
117+
"--include cargo-0.60.0,cargo-0.87.1,stm32f4-0.14.0,webrender-2022",
118+
"--exclude cargo-0.60.0,cargo-0.87.1,stm32f4-0.14.0,webrender-2022",
119119
]
120120
PROFILES: [
121121
"Check,Debug,Doc",

‎collector/compile-benchmarks/README.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,8 @@ They mostly consist of real-world crates.
2323
`N` value from 1 to 1024.
2424
- **cargo-0.60.0**: The Rust package manager. A large program, and an important
2525
part of the Rust ecosystem.
26+
- **cargo-0.87.1**: The Rust package manager. A large program, and an important
27+
part of the Rust ecosystem.
2628
- **clap-3.1.6**: A command line argument parser library. A crate used by many
2729
Rust programs.
2830
- **cranelift-codegen-0.82.1**: The largest crate from a code generator. Used by

‎collector/compile-benchmarks/REUSE.toml‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,11 @@ path = "cargo-0.60.0/**"
3232
SPDX-FileCopyrightText = "The Rust Project Developers (see https://thanks.rust-lang.org)"
3333
SPDX-License-Identifier = "MIT OR Apache-2.0"
3434

35+
[[annotations]]
36+
path = "cargo-0.87.1/**"
37+
SPDX-FileCopyrightText = "The Rust Project Developers (see https://thanks.rust-lang.org)"
38+
SPDX-License-Identifier = "MIT OR Apache-2.0"
39+
3540
[[annotations]]
3641
path = "clap-3.1.6/**"
3742
SPDX-FileCopyrightText = "clap contributors"

‎collector/compile-benchmarks/cargo-0.87.1/.cargo/config.toml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
[alias]
2+
build-man = "run --package xtask-build-man --"
3+
stale-label = "run --package xtask-stale-label --"
4+
bump-check = "run --package xtask-bump-check --"
5+
lint-docs = "run --package xtask-lint-docs --"
6+
7+
[env]
8+
# HACK: Until this is stabilized, `snapbox`s polyfill could get confused
9+
# inside of the rust-lang/rust repo because it looks for the furthest-away `Cargo.toml`
10+
CARGO_RUSTC_CURRENT_DIR = { value = "", relative = true }

‎collector/compile-benchmarks/cargo-0.87.1/.cargo_vcs_info.json‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
{
2+
"git": {
3+
"sha1": "ab9915ce5d9de5e1f2fb3c10378a353ca88693f2"
4+
},
5+
"path_in_vcs": ""
6+
}

‎collector/compile-benchmarks/cargo-0.87.1/.github/ISSUE_TEMPLATE/bug_report.yml‎

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
name: Bug Report
2+
description: Create a report to help us improve
3+
labels: ["C-bug", "S-triage"]
4+
body:
5+
- type: markdown
6+
attributes:
7+
value: Thanks for filing a 🐛 bug report 😄!
8+
- type: textarea
9+
id: problem
10+
attributes:
11+
label: Problem
12+
description: >
13+
Please provide a clear and concise description of what the bug is,
14+
including what currently happens and what you expected to happen.
15+
validations:
16+
required: true
17+
- type: textarea
18+
id: steps
19+
attributes:
20+
label: Steps
21+
description: Please list the steps to reproduce the bug.
22+
placeholder: |
23+
1.
24+
2.
25+
3.
26+
- type: textarea
27+
id: possible-solutions
28+
attributes:
29+
label: Possible Solution(s)
30+
description: >
31+
Not obligatory, but suggest a fix/reason for the bug,
32+
or ideas how to implement the addition or change.
33+
- type: textarea
34+
id: notes
35+
attributes:
36+
label: Notes
37+
description: Provide any additional notes that might be helpful.
38+
- type: textarea
39+
id: version
40+
attributes:
41+
label: Version
42+
description: Please paste the output of running `cargo version --verbose`.
43+
render: text

‎collector/compile-benchmarks/cargo-0.87.1/.github/ISSUE_TEMPLATE/config.yml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
contact_links:
2+
- name: Question
3+
url: https://users.rust-lang.org
4+
about: >
5+
Got a question about Cargo? Ask the community on the user forum.
6+
- name: Inspiring Idea
7+
url: https://internals.rust-lang.org/c/tools-and-infrastructure/cargo
8+
about: >
9+
Need more discussions with your next big idea?
10+
Reach out the coummunity on the internals forum.

‎collector/compile-benchmarks/cargo-0.87.1/.github/ISSUE_TEMPLATE/feature_request.yml‎

Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
name: Feature Request
2+
description: Suggest an idea for enhancing Cargo
3+
labels: ["C-feature-request", "S-triage"]
4+
body:
5+
- type: markdown
6+
attributes:
7+
value: |
8+
Thanks for filing a 🙋 feature request 😄!
9+
10+
If the feature request is relatively small and already with a possible solution, this might be the place for you.
11+
12+
If you are brewing a big feature that needs feedback from the community, [the internal forum] is the best fit, especially for pre-RFC. You can also talk the idea over with other developers in [#t-cargo Zulip stream].
13+
14+
[the internal forum]: https://internals.rust-lang.org/c/tools-and-infrastructure/cargo/15
15+
[#t-cargo Zulip stream]: https://rust-lang.zulipchat.com/#narrow/stream/246057-t-cargo
16+
- type: textarea
17+
id: problem
18+
attributes:
19+
label: Problem
20+
description: >
21+
Please provide a clear description of your use case and the problem
22+
this feature request is trying to solve.
23+
validations:
24+
required: true
25+
- type: textarea
26+
id: solution
27+
attributes:
28+
label: Proposed Solution
29+
description: >
30+
Please provide a clear and concise description of what you want to happen.
31+
- type: textarea
32+
id: notes
33+
attributes:
34+
label: Notes
35+
description: Provide any additional context or information that might be helpful.

‎collector/compile-benchmarks/cargo-0.87.1/.github/ISSUE_TEMPLATE/tracking_issue.yml‎

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
name: Tracking Issue
2+
description: A tracking issue for an accepted feature or RFC in Cargo.
3+
title: "Tracking Issue for _FEATURE_NAME_"
4+
labels: ["C-tracking-issue"]
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: >
9+
Thank you for creating a tracking issue! Tracking issues are for tracking an
10+
accepted feature or RFC from implementation to stabilization. Please do not
11+
file a tracking issue until the feature or RFC has been approved.
12+
- type: textarea
13+
id: summary
14+
attributes:
15+
label: Summary
16+
description: Please provide a very brief summary of the feature.
17+
value: |
18+
RFC: [#NNNN](https://github.com/rust-lang/rfcs/pull/NNNN) <!-- If this is an RFC -->
19+
Original issue: #NNNN <!-- if there is a related issue that spawned this feature -->
20+
Implementation: #NNNN <!-- link to the PR that implemented this feature if applicable -->
21+
Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#my-feature
22+
23+
Please enter a short, one-sentence description here.
24+
validations:
25+
required: true
26+
- type: textarea
27+
id: unresolved
28+
attributes:
29+
label: Unresolved Issues
30+
description: List issues that have not yet been resolved.
31+
placeholder: |
32+
* [ ] Make a list of any known implementation or design issues.
33+
- type: textarea
34+
id: future
35+
attributes:
36+
label: Future Extensions
37+
description: >
38+
An optional section where you can mention where the feature may be
39+
extended in the future, but is explicitly not intended to
40+
address.
41+
- type: textarea
42+
id: about
43+
attributes:
44+
label: About tracking issues
45+
description: Please include this notice in the issue.
46+
value: |
47+
Tracking issues are used to record the overall progress of implementation.
48+
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
49+
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
50+
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

‎collector/compile-benchmarks/cargo-0.87.1/.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
<!--
2+
Thanks for submitting a pull request 🎉! Here are some tips for you:
3+
4+
* If this is your first contribution, read "Cargo Contribution Guide" first:
5+
https://doc.crates.io/contrib/
6+
* Run `cargo fmt --all` to format your code changes.
7+
* Small commits and pull requests are always preferable and easy to review.
8+
* If your idea is large and needs feedback from the community, read how:
9+
https://doc.crates.io/contrib/process/#working-on-large-features
10+
* Cargo takes care of compatibility. Read our design principles:
11+
https://doc.crates.io/contrib/design.html
12+
* When changing help text of cargo commands, follow the steps to generate docs:
13+
https://github.com/rust-lang/cargo/tree/master/src/doc#building-the-man-pages
14+
* If your PR is not finished, set it as "draft" PR or add "WIP" in its title.
15+
* It's ok to use the CI resources to test your PR, but please don't abuse them.
16+
17+
### What does this PR try to resolve?
18+
19+
Explain the motivation behind this change.
20+
A clear overview along with an in-depth explanation are helpful.
21+
22+
You can use `Fixes #<issue number>` to associate this PR to an existing issue.
23+
24+
### How should we test and review this PR?
25+
26+
Demonstrate how you test this change and guide reviewers through your PR.
27+
With a smooth review process, a pull request usually gets reviewed quicker.
28+
29+
If you don't know how to write and run your tests, please read the guide:
30+
https://doc.crates.io/contrib/tests
31+
32+
### Additional information
33+
34+
Other information you want to mention in this PR, such as prior arts,
35+
future extensions, an unresolved problem, or a TODO list.
36+
-->

0 commit comments

Comments
 (0)