-
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 4 pull requests #124564
Rollup of 4 pull requests #124564
Commits on Apr 30, 2024
-
write git-commit-{sha,info} for Cargo in source tarballs
This will allow Cargo's build script to pick it up, and populate the correct git information in its version output.
Configuration menu - View commit details
-
Copy full SHA for 7a5038f - Browse repository at this point
Copy the full SHA 7a5038fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 7032c92 - Browse repository at this point
Copy the full SHA 7032c92View commit details -
Configuration menu - View commit details
-
Copy full SHA for e0ec71f - Browse repository at this point
Copy the full SHA e0ec71fView commit details -
Configuration menu - View commit details
-
Copy full SHA for c2fd6ed - Browse repository at this point
Copy the full SHA c2fd6edView commit details -
Rollup merge of rust-lang#124280 - beetrees:repr128-test-rmake, r=jie…
…youxu Port repr128-dwarf run-make test to rmake This PR ports the repr128-dwarf run-make test to rmake, using the `gimli` crate instead of the `llvm-dwarfdump` command. Note that this PR changes `rmake.rs` files to be compiled with the 2021 edition (previously no edition was passed to `rustc`, meaning they were compiled with the 2015 edition). This means that `panic!("{variable}")` will now work as expected in `rmake.rs` files (there's already a usage in the [wasm-symbols-not-exported test](https://github.com/rust-lang/rust/blob/aca749eefceaed0cda19a7ec5e472fce9387bc00/tests/run-make/wasm-symbols-not-exported/rmake.rs#L34) that this will fix). Tracking issue: rust-lang#121876
Configuration menu - View commit details
-
Copy full SHA for ce18639 - Browse repository at this point
Copy the full SHA ce18639View commit details -
Rollup merge of rust-lang#124299 - clubby789:106269-test, r=nikic
Add test for issue 106269 Closes rust-lang#106269 Made this an assembly test as the LLVM codegen is still quite verbose and doesn't really indicate the behaviour we want
Configuration menu - View commit details
-
Copy full SHA for 4b6c191 - Browse repository at this point
Copy the full SHA 4b6c191View commit details -
Rollup merge of rust-lang#124553 - ferrocene:pa-cargo-git-info, r=onu…
…r-ozkan Write `git-commit-{sha,info}` for Cargo in source tarballs Right now Cargo doesn't populate the commit hash or date in its version output when it's built from the plain source tarball. That's because we don't include the git information for it, and Cargo's build script doesn't pick it up. This PR *partially* solves the problem by storing the git information for Cargo in `src/tools/cargo` in the plain source tarball. We store separate information because even when built in CI Cargo uses its own git information rather than Rust's. This PR will also require a change in the Cargo repository to consume this information (rust-lang/cargo#13832), but it doesn't have to be blocked on the Cargo PR being merged.
Configuration menu - View commit details
-
Copy full SHA for 9ef81e0 - Browse repository at this point
Copy the full SHA 9ef81e0View commit details -
Rollup merge of rust-lang#124561 - GuillaumeGomez:run-make-normalize,…
… r=jieyouxu Add `normalize()` in run-make `Diff` type I need it to do the same as: ``` //@ normalize-stdout-test "finished in \d+\.\d+s" -> "finished in $$TIME" ``` in doctests. I need it in particular for the rust-lang#123974 PR (which contains this commit until this PR current PR is merged). cc `@Urgau` r? `@jieyouxu`
Configuration menu - View commit details
-
Copy full SHA for 7350a7f - Browse repository at this point
Copy the full SHA 7350a7fView commit details