-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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 #104228
Rollup of 11 pull requests #104228
Commits on Nov 4, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 1bcf9fa - Browse repository at this point
Copy the full SHA 1bcf9faView commit details -
Configuration menu - View commit details
-
Copy full SHA for 3ea4165 - Browse repository at this point
Copy the full SHA 3ea4165View commit details
Commits on Nov 6, 2022
-
Configuration menu - View commit details
-
Copy full SHA for c199a39 - Browse repository at this point
Copy the full SHA c199a39View commit details -
Configuration menu - View commit details
-
Copy full SHA for a9edee7 - Browse repository at this point
Copy the full SHA a9edee7View commit details -
Configuration menu - View commit details
-
Copy full SHA for 5f9899b - Browse repository at this point
Copy the full SHA 5f9899bView commit details -
Configuration menu - View commit details
-
Copy full SHA for dc1f1a8 - Browse repository at this point
Copy the full SHA dc1f1a8View commit details -
Use aapcs for efiapi calling convention on arm
On arm, llvm treats the C calling convention as `aapcs` on soft-float targets and `aapcs-vfp` on hard-float targets [1]. UEFI specifies in the arm calling convention that floating point extensions aren't used [2], so always translate `efiapi` to `aapcs` on arm. [1]: rust-lang/compiler-builtins#116 (comment) [2]: https://uefi.org/specs/UEFI/2.10/02_Overview.html#detailed-calling-convention rust-lang#65815
Configuration menu - View commit details
-
Copy full SHA for 42cbb40 - Browse repository at this point
Copy the full SHA 42cbb40View commit details
Commits on Nov 7, 2022
-
Configuration menu - View commit details
-
Copy full SHA for cebce1e - Browse repository at this point
Copy the full SHA cebce1eView commit details
Commits on Nov 8, 2022
-
Configuration menu - View commit details
-
Copy full SHA for 667b15b - Browse repository at this point
Copy the full SHA 667b15bView commit details -
Configuration menu - View commit details
-
Copy full SHA for 9e7d228 - Browse repository at this point
Copy the full SHA 9e7d228View commit details -
Configuration menu - View commit details
-
Copy full SHA for 56e59bc - Browse repository at this point
Copy the full SHA 56e59bcView commit details
Commits on Nov 9, 2022
-
Configuration menu - View commit details
-
Copy full SHA for aa5a326 - Browse repository at this point
Copy the full SHA aa5a326View commit details -
Configuration menu - View commit details
-
Copy full SHA for 91b4e7c - Browse repository at this point
Copy the full SHA 91b4e7cView commit details -
Ignore "Change InferCtxtBuilder from enter to build" in git blame
Because it changed the indentation of many things, this commit caused a lot of diff with no functional changes, so we should ignore it.
Configuration menu - View commit details
-
Copy full SHA for 35ef05a - Browse repository at this point
Copy the full SHA 35ef05aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 4c197c0 - Browse repository at this point
Copy the full SHA 4c197c0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 8f9bc6d - Browse repository at this point
Copy the full SHA 8f9bc6dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 0e804b4 - Browse repository at this point
Copy the full SHA 0e804b4View commit details -
Configuration menu - View commit details
-
Copy full SHA for dc76687 - Browse repository at this point
Copy the full SHA dc76687View commit details -
Configuration menu - View commit details
-
Copy full SHA for 75b5a98 - Browse repository at this point
Copy the full SHA 75b5a98View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9f0e376 - Browse repository at this point
Copy the full SHA 9f0e376View commit details -
Configuration menu - View commit details
-
Copy full SHA for fbce7de - Browse repository at this point
Copy the full SHA fbce7deView commit details -
Configuration menu - View commit details
-
Copy full SHA for e807cb3 - Browse repository at this point
Copy the full SHA e807cb3View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9568138 - Browse repository at this point
Copy the full SHA 9568138View commit details
Commits on Nov 10, 2022
-
remove redundent "<>" for ty::Slice with reference type
this fix rust-lang#103271
Yiming Lei committedNov 10, 2022 Configuration menu - View commit details
-
Copy full SHA for 0b6934d - Browse repository at this point
Copy the full SHA 0b6934dView commit details -
Rollup merge of rust-lang#102763 - compiler-errors:nits, r=cjgillot
Some diagnostic-related nits 1. Use `&mut Diagnostic` instead of `&mut DiagnosticBuilder<'_, T>` 2. Make `diag.span_suggestions` take an `IntoIterator` instead of `Iterator`, just to remove some `.into_iter` calls on the caller. idk if I should add a lint to make sure people use `&mut Diagnostic` instead of `&mut DiagnosticBuilder<'_, T>` in cases where we're just, e.g., adding subdiagnostics to the diagnostic... maybe a followup.
Configuration menu - View commit details
-
Copy full SHA for 592c024 - Browse repository at this point
Copy the full SHA 592c024View commit details -
Rollup merge of rust-lang#103443 - mucinoab:recover-colon-as-path-sep…
…aretor, r=compiler-errors Parser: Recover from using colon as path separator in imports I don't know if this is the right approach, any feedback is welcome. r? ``@compiler-errors`` Fixes rust-lang#103269
Configuration menu - View commit details
-
Copy full SHA for 994b5db - Browse repository at this point
Copy the full SHA 994b5dbView commit details -
Rollup merge of rust-lang#103636 - chenyukang:yukang/fix-103587-sugg-…
…if-let, r=jackh276,davidtwco Recover from common if let syntax mistakes/typos Fixes rust-lang#103587
Configuration menu - View commit details
-
Copy full SHA for 47b7512 - Browse repository at this point
Copy the full SHA 47b7512View commit details -
Rollup merge of rust-lang#103675 - lyming2007:issue-103271-fix, r=fee…
…1-dead remove redundent "<>" for ty::Slice with reference type this fix rust-lang#103271
Configuration menu - View commit details
-
Copy full SHA for c729acb - Browse repository at this point
Copy the full SHA c729acbView commit details -
Rollup merge of rust-lang#104046 - RalfJung:run-miri-run, r=oli-obk
bootstrap: add support for running Miri on a file This enables: ``` ./x.py run src/tools/miri --stage 0 --args src/tools/miri/tests/pass/hello.rs ``` That can be super helpful for debugging. Also avoid sharing the Miri sysroot dir with a system-wide (rustup-managed) installation of Miri. Fixes rust-lang#76666
Configuration menu - View commit details
-
Copy full SHA for 60d20b1 - Browse repository at this point
Copy the full SHA 60d20b1View commit details -
Rollup merge of rust-lang#104060 - ink-feather-org:const_hash, r=fee1…
…-dead Make `Hash`, `Hasher` and `BuildHasher` `#[const_trait]` and make `Sip` const `Hasher` This PR enables using Hashes in const context. r? `@fee1-dead`
Configuration menu - View commit details
-
Copy full SHA for 3d848c2 - Browse repository at this point
Copy the full SHA 3d848c2View commit details -
Rollup merge of rust-lang#104077 - nicholasbishop:bishop-uefi-aapcs, …
…r=nagisa Use aapcs for efiapi calling convention on arm On arm, [llvm treats the C calling convention as `aapcs` on soft-float targets and `aapcs-vfp` on hard-float targets](rust-lang/compiler-builtins#116 (comment)). UEFI specifies in the arm calling convention that [floating point extensions aren't used](https://uefi.org/specs/UEFI/2.10/02_Overview.html#detailed-calling-convention), so always translate `efiapi` to `aapcs` on arm. rust-lang#65815
Configuration menu - View commit details
-
Copy full SHA for 5694a33 - Browse repository at this point
Copy the full SHA 5694a33View commit details -
Rollup merge of rust-lang#104115 - GuillaumeGomez:migrate-crate-searc…
…h-div, r=notriddle Migrate crate-search element to CSS variables There should no UI changes. r? ``@notriddle``
Configuration menu - View commit details
-
Copy full SHA for dac9fb7 - Browse repository at this point
Copy the full SHA dac9fb7View commit details -
Rollup merge of rust-lang#104190 - Nilstrieb:patch-1, r=compiler-errors
Ignore "Change InferCtxtBuilder from enter to build" in git blame Because it changed the indentation of many things, this commit caused a lot of diff with no functional changes, so we should ignore it. r? ``@compiler-errors`` as you've complained about this before The relevant commit: rust-lang@283abbf
Configuration menu - View commit details
-
Copy full SHA for e2fee15 - Browse repository at this point
Copy the full SHA e2fee15View commit details -
Rollup merge of rust-lang#104194 - BoxyUwU:early_binder_docs, r=compi…
…ler-errors `EarlyBinder` docs
Configuration menu - View commit details
-
Copy full SHA for f7b8884 - Browse repository at this point
Copy the full SHA f7b8884View commit details -
Rollup merge of rust-lang#104201 - GuillaumeGomez:gui-test-check-file…
…-errors, r=notriddle Add check in GUI test for file loading failure Since rust-lang#101702, some resources location need to be updated in case their content changed because then their hash will change too. This will prevent errors like rust-lang#104114 to happen again. The second commit is to prevent CORS errors: when a file is linked from a file itself imported, the web browser considers they come from a different domain and therefore triggers the error. The option tells the web browser to ignore this case. cc ``@jsha`` r? ``@notriddle``
Configuration menu - View commit details
-
Copy full SHA for d829264 - Browse repository at this point
Copy the full SHA d829264View commit details