-
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 9 pull requests #78451
Rollup of 9 pull requests #78451
Commits on Oct 25, 2020
-
Configuration menu - View commit details
-
Copy full SHA for 9dadcf8 - Browse repository at this point
Copy the full SHA 9dadcf8View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0e419ef - Browse repository at this point
Copy the full SHA 0e419efView commit details
Commits on Oct 26, 2020
-
Configuration menu - View commit details
-
Copy full SHA for 00abef1 - Browse repository at this point
Copy the full SHA 00abef1View commit details -
Configuration menu - View commit details
-
Copy full SHA for 8546a80 - Browse repository at this point
Copy the full SHA 8546a80View commit details -
Configuration menu - View commit details
-
Copy full SHA for 60bcc58 - Browse repository at this point
Copy the full SHA 60bcc58View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0cf3ce4 - Browse repository at this point
Copy the full SHA 0cf3ce4View commit details -
Configuration menu - View commit details
-
Copy full SHA for 174ed0c - Browse repository at this point
Copy the full SHA 174ed0cView commit details -
build-manifest: add BUILD_MANIFEST_CHECKSUM_CACHE
The checksum cache allows to reuse the calculated checksums between build-manifest and promote-release, or between multiple invocations of build-manifest.
Configuration menu - View commit details
-
Copy full SHA for c2f4bbd - Browse repository at this point
Copy the full SHA c2f4bbdView commit details -
Configuration menu - View commit details
-
Copy full SHA for 53fa22a - Browse repository at this point
Copy the full SHA 53fa22aView commit details -
Configuration menu - View commit details
-
Copy full SHA for a3623e0 - Browse repository at this point
Copy the full SHA a3623e0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 8cf1b0e - Browse repository at this point
Copy the full SHA 8cf1b0eView commit details -
Configuration menu - View commit details
-
Copy full SHA for a2f4afe - Browse repository at this point
Copy the full SHA a2f4afeView commit details -
Configuration menu - View commit details
-
Copy full SHA for 8b65df0 - Browse repository at this point
Copy the full SHA 8b65df0View commit details -
Configuration menu - View commit details
-
Copy full SHA for ce95122 - Browse repository at this point
Copy the full SHA ce95122View commit details -
Configuration menu - View commit details
-
Copy full SHA for 5643a06 - Browse repository at this point
Copy the full SHA 5643a06View commit details -
Configuration menu - View commit details
-
Copy full SHA for 737bfef - Browse repository at this point
Copy the full SHA 737bfefView commit details -
Configuration menu - View commit details
-
Copy full SHA for 1bcd245 - Browse repository at this point
Copy the full SHA 1bcd245View commit details -
Configuration menu - View commit details
-
Copy full SHA for 576eb2a - Browse repository at this point
Copy the full SHA 576eb2aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 5ac1688 - Browse repository at this point
Copy the full SHA 5ac1688View commit details -
Configuration menu - View commit details
-
Copy full SHA for 6ba127d - Browse repository at this point
Copy the full SHA 6ba127dView commit details -
Implement -Z function-sections=yes|no
This lets rustc users tweak whether all functions should be put in their own TEXT section, using whatever default value the target defines if the flag is missing.
Configuration menu - View commit details
-
Copy full SHA for 0569422 - Browse repository at this point
Copy the full SHA 0569422View commit details -
Configuration menu - View commit details
-
Copy full SHA for cb8b901 - Browse repository at this point
Copy the full SHA cb8b901View commit details
Commits on Oct 27, 2020
-
Configuration menu - View commit details
-
Copy full SHA for 39941e6 - Browse repository at this point
Copy the full SHA 39941e6View commit details -
Configuration menu - View commit details
-
Copy full SHA for 650e3cb - Browse repository at this point
Copy the full SHA 650e3cbView commit details -
Configuration menu - View commit details
-
Copy full SHA for 572cd35 - Browse repository at this point
Copy the full SHA 572cd35View commit details -
Configuration menu - View commit details
-
Copy full SHA for da64d07 - Browse repository at this point
Copy the full SHA da64d07View commit details -
Configuration menu - View commit details
-
Copy full SHA for 99320b9 - Browse repository at this point
Copy the full SHA 99320b9View commit details -
Configuration menu - View commit details
-
Copy full SHA for b01c74b - Browse repository at this point
Copy the full SHA b01c74bView commit details -
Rollup merge of #75671 - nathanwhit:cstring-temp-lint, r=oli-obk
Uplift `temporary-cstring-as-ptr` lint from `clippy` into rustc The general consensus seems to be that this lint covers a common enough mistake to warrant inclusion in rustc. The diagnostic message might need some tweaking, as I'm not sure the use of second-person perspective matches the rest of rustc, but I'd like to hear others' thoughts on that. (cc #53224). r? @oli-obk
Configuration menu - View commit details
-
Copy full SHA for b2e935d - Browse repository at this point
Copy the full SHA b2e935dView commit details -
Rollup merge of #78365 - lcnr:const-eval-obj-safety, r=oli-obk
check object safety of generic constants As `Self` can only be effectively used in constants with `const_evaluatable_checked` this should not matter outside of it. Implements the first item of #72219 > Object safety interactions with constants r? @oli-obk for now cc @nikomatsakis
Configuration menu - View commit details
-
Copy full SHA for 3861024 - Browse repository at this point
Copy the full SHA 3861024View commit details -
Rollup merge of #78378 - nagisa:nagisa/libc-up, r=Mark-Simulacrum
libc: 0.2.79 -> 0.2.80 This PR bumps the version of the libc crate from 0.2.79 to 0.2.80 in order to hopefully fix a build failure when building the standard library for the tier 3 `x86_64-unknown-dragonfly` target.
Configuration menu - View commit details
-
Copy full SHA for 3e49068 - Browse repository at this point
Copy the full SHA 3e49068View commit details -
Rollup merge of #78408 - Aaron1011:fix/remove-foreign-tokens, r=oli-obk
Configuration menu - View commit details
-
Copy full SHA for 944a4b0 - Browse repository at this point
Copy the full SHA 944a4b0View commit details -
Rollup merge of #78409 - pietroalbini:build-manifest-checksum-cache, …
…r=Mark-Simulacrum Add checksums cache to build-manifest During the release process we're currently calculating the SHA256 of each file three times: 1. In `build-manifest`, to fill the `hash = "f00"` keys of the manifests. 2. In `promote-release`, to generate the `.sha256` files. 3. In `promote-release`, to generate the `.asc` GPG signatures. Calculations 1. and 2. could be merged into a single one if there was a way for `build-manifest` to pass the checksums it generated over to `promote-release`. Unfortunately calculation 3. can't be merged as GPG requires extra metadata to be hashed. This PR adds support for merging 1. and 2. by creating the `BUILD_MANIFEST_CHECKSUM_CACHE` environment variable, which points to a JSON file storing a cache of all the calculated checksums. `build-manifest` will load it at startup and avoid generating existing checksums, and it will dump its internal checksums cache into it when it exits successfully. This PR also allows to run `build-manifest` multiple times without the need to wait for checksums to be calculated in the following invocations. The speedup will allow to work torwards a fix for rust-lang/promote-release#15 without impacting the release process duration nor our storage costs. This PR can be reviewed commit-by-commit. r? @Mark-Simulacrum
Configuration menu - View commit details
-
Copy full SHA for 163b322 - Browse repository at this point
Copy the full SHA 163b322View commit details -
Rollup merge of #78414 - nox:function-sections, r=nagisa,bjorn3
Implement -Z function-sections=yes|no This lets rustc users tweak whether all functions should be put in their own TEXT section, using whatever default value the target defines if the flag is missing. I'm having fun experimenting with musl libc and trying to implement the start symbol in Rust, that means avoiding code that requires relocations, and AFAIK putting everything in its own section makes the toolchain generate `GOTPCREL` relocations for symbols that could use plain old PC-relative addressing (at least on `x86_64`) if they were all in the same section.
Configuration menu - View commit details
-
Copy full SHA for f29e191 - Browse repository at this point
Copy the full SHA f29e191View commit details -
Rollup merge of #78415 - tgnottingham:expn_id_tag_hash, r=Aaron1011
rustc_span: avoid hashing ExpnId tag when using cached hash
Configuration menu - View commit details
-
Copy full SHA for afbc67b - Browse repository at this point
Copy the full SHA afbc67bView commit details -
Rollup merge of #78431 - Rustin-Liu:rustin-patch-lint, r=estebank
Prefer new associated numeric consts in float error messages CC #78382
Configuration menu - View commit details
-
Copy full SHA for 2ddaa60 - Browse repository at this point
Copy the full SHA 2ddaa60View commit details -
Rollup merge of #78447 - bugadani:typo, r=matthewjasper
Fix typo in comment I hope I got all the typos in that word. :)
Configuration menu - View commit details
-
Copy full SHA for 733e3c5 - Browse repository at this point
Copy the full SHA 733e3c5View commit details