-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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 #111165
Rollup of 11 pull requests #111165
Commits on Feb 16, 2023
-
Configuration menu - View commit details
-
Copy full SHA for 9622cde - Browse repository at this point
Copy the full SHA 9622cdeView commit details
Commits on Apr 17, 2023
-
Configuration menu - View commit details
-
Copy full SHA for 1a7132d - Browse repository at this point
Copy the full SHA 1a7132dView commit details -
rustdoc: restructure type search engine to pick-and-use IDs
This change makes it so, instead of mixing string distance with type unification, function signature search works by mapping names to IDs at the start, reporting to the user any cases where it had to make corrections, and then matches with IDs when going through the items. This only changes function searches. Name searches are left alone, and corrections are only done when there's a single item in the search query.
Configuration menu - View commit details
-
Copy full SHA for 4c11822 - Browse repository at this point
Copy the full SHA 4c11822View commit details
Commits on Apr 19, 2023
-
Configuration menu - View commit details
-
Copy full SHA for b6f81e0 - Browse repository at this point
Copy the full SHA b6f81e0View commit details
Commits on Apr 20, 2023
-
Configuration menu - View commit details
-
Copy full SHA for e0a7462 - Browse repository at this point
Copy the full SHA e0a7462View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7529d87 - Browse repository at this point
Copy the full SHA 7529d87View commit details -
Configuration menu - View commit details
-
Copy full SHA for 395840c - Browse repository at this point
Copy the full SHA 395840cView commit details
Commits on Apr 29, 2023
-
Remove ENTRY_LIMIT maximum checking and set it to 900
The number 900 is safely below github's limit of 1000 entries for a directory. PRs to move tests can still decrease the sizes of various directories, but adjusting the limit won't be neccessary any more. In general, the limit is a bad tool to direct people to put tests into fitting directories because when those are available, usually the limit is not hit, while the limit is hit in directories that have a weak substructure themselves.
Configuration menu - View commit details
-
Copy full SHA for e498402 - Browse repository at this point
Copy the full SHA e498402View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4375d3b - Browse repository at this point
Copy the full SHA 4375d3bView commit details
Commits on May 2, 2023
-
Configuration menu - View commit details
-
Copy full SHA for 9fba262 - Browse repository at this point
Copy the full SHA 9fba262View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4d04a06 - Browse repository at this point
Copy the full SHA 4d04a06View commit details -
Remove
[]
<->()
From
convertions... with this convertions some tests fail :(
Configuration menu - View commit details
-
Copy full SHA for 04305c0 - Browse repository at this point
Copy the full SHA 04305c0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 36f8693 - Browse repository at this point
Copy the full SHA 36f8693View commit details -
Configuration menu - View commit details
-
Copy full SHA for 522eeba - Browse repository at this point
Copy the full SHA 522eebaView commit details -
Configuration menu - View commit details
-
Copy full SHA for 6382876 - Browse repository at this point
Copy the full SHA 6382876View commit details
Commits on May 3, 2023
-
Correctly convert an NT path to a Win32 path
This can be done by simply changing the `\??\` prefix to `\\?\` and then attempting to convert to a user path. Currently it simply strips off the prefix which could lead to the wrong path being returned (e.g. if it's not a drive path or if the path contains trailing spaces, etc).
Configuration menu - View commit details
-
Copy full SHA for 6e37784 - Browse repository at this point
Copy the full SHA 6e37784View commit details -
Configuration menu - View commit details
-
Copy full SHA for 109a47f - Browse repository at this point
Copy the full SHA 109a47fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 4fec8a3 - Browse repository at this point
Copy the full SHA 4fec8a3View commit details -
Configuration menu - View commit details
-
Copy full SHA for 6f6c379 - Browse repository at this point
Copy the full SHA 6f6c379View commit details -
Use builtin FFX isolation for Fuchsia test runner
FFX has new builtin support for isolating the daemon's environment. This switches the manual isolation originally written to that new builtin feature.
David Koloski committedMay 3, 2023 Configuration menu - View commit details
-
Copy full SHA for e973836 - Browse repository at this point
Copy the full SHA e973836View commit details -
Configuration menu - View commit details
-
Copy full SHA for de10516 - Browse repository at this point
Copy the full SHA de10516View commit details -
Add cross-language LLVM CFI support to the Rust compiler
This commit adds cross-language LLVM Control Flow Integrity (CFI) support to the Rust compiler by adding the `-Zsanitizer-cfi-normalize-integers` option to be used with Clang `-fsanitize-cfi-icall-normalize-integers` for normalizing integer types (see https://reviews.llvm.org/D139395). It provides forward-edge control flow protection for C or C++ and Rust -compiled code "mixed binaries" (i.e., for when C or C++ and Rust -compiled code share the same virtual address space). For more information about LLVM CFI and cross-language LLVM CFI support for the Rust compiler, see design document in the tracking issue rust-lang#89653. Cross-language LLVM CFI can be enabled with -Zsanitizer=cfi and -Zsanitizer-cfi-normalize-integers, and requires proper (i.e., non-rustc) LTO (i.e., -Clinker-plugin-lto).
Configuration menu - View commit details
-
Copy full SHA for 004aa15 - Browse repository at this point
Copy the full SHA 004aa15View commit details -
Update documentation for LLVM CFI support
This commit updates the documentation for the LLVM Control Flow Integrity (CFI) support in the Rust compiler.
Configuration menu - View commit details
-
Copy full SHA for 9a02f65 - Browse repository at this point
Copy the full SHA 9a02f65View commit details -
Rollup merge of rust-lang#97594 - WaffleLapkin:array_tuple_conv, r=Ch…
…risDenton Implement tuple<->array convertions via `From` This PR adds the following impls that convert between homogeneous tuples and arrays of the corresponding lengths: ```rust impl<T> From<[T; 1]> for (T,) { ... } impl<T> From<[T; 2]> for (T, T) { ... } /* ... */ impl<T> From<[T; 12]> for (T, T, T, T, T, T, T, T, T, T, T, T) { ... } impl<T> From<(T,)> for [T; 1] { ... } impl<T> From<(T, T)> for [T; 2] { ... } /* ... */ impl<T> From<(T, T, T, T, T, T, T, T, T, T, T, T)> for [T; 12] { ... } ``` IMO these are quite uncontroversial but note that they are, just like any other trait impls, insta-stable.
Configuration menu - View commit details
-
Copy full SHA for 0830f35 - Browse repository at this point
Copy the full SHA 0830f35View commit details -
Rollup merge of rust-lang#105452 - rcvalle:rust-cfi-3, r=bjorn3
Add cross-language LLVM CFI support to the Rust compiler This PR adds cross-language LLVM Control Flow Integrity (CFI) support to the Rust compiler by adding the `-Zsanitizer-cfi-normalize-integers` option to be used with Clang `-fsanitize-cfi-icall-normalize-integers` for normalizing integer types (see https://reviews.llvm.org/D139395). It provides forward-edge control flow protection for C or C++ and Rust -compiled code "mixed binaries" (i.e., for when C or C++ and Rust -compiled code share the same virtual address space). For more information about LLVM CFI and cross-language LLVM CFI support for the Rust compiler, see design document in the tracking issue rust-lang#89653. Cross-language LLVM CFI can be enabled with -Zsanitizer=cfi and -Zsanitizer-cfi-normalize-integers, and requires proper (i.e., non-rustc) LTO (i.e., -Clinker-plugin-lto). Thank you again, `@bjorn3,` `@nikic,` `@samitolvanen,` and the Rust community for all the help!
Configuration menu - View commit details
-
Copy full SHA for 3e797ec - Browse repository at this point
Copy the full SHA 3e797ecView commit details -
Rollup merge of rust-lang#105695 - joboet:remove_generic_parker, r=m-…
…ou-se Replace generic thread parker with explicit no-op parker With rust-lang#98391 merged, all platforms supporting threads now have their own parking implementations. Therefore, the generic implementation can be removed. On the remaining platforms (really just WASM without atomics), parking is not supported, so calls to `thread::park` now return instantly, which is [allowed by their API](https://doc.rust-lang.org/nightly/std/thread/fn.park.html). This is a change in behaviour, as spurious wakeups do not currently occur since all platforms guard against them. It is invalid to depend on this, but I'm still going to tag this as libs-api for confirmation. ```@rustbot``` label +T-libs +T-libs-api +A-atomic r? rust-lang/libs
Configuration menu - View commit details
-
Copy full SHA for faa3169 - Browse repository at this point
Copy the full SHA faa3169View commit details -
Rollup merge of rust-lang#107978 - ChrisDenton:nt-to-win32, r=m-ou-se
Correctly convert an NT path to a Win32 path in `read_link` This can be done by simply changing the `\??\` prefix to `\\?\`. Currently it strips off the prefix which could lead to the wrong path being returned (e.g. if it's not a drive path or if the path contains trailing spaces, etc). r? libs
Configuration menu - View commit details
-
Copy full SHA for c0f08bb - Browse repository at this point
Copy the full SHA c0f08bbView commit details -
Rollup merge of rust-lang#110371 - notriddle:notriddle/search-correct…
…ions, r=GuillaumeGomez rustdoc: restructure type search engine to pick-and-use IDs Fixes rust-lang#110029 Preview: https://notriddle.com/rustdoc-demo-html-3/search-corrections/std/index.html?search=-%3E%20streaming ![image](https://user-images.githubusercontent.com/1593513/233494900-ae77d5b4-e395-41f8-bbac-53ee55bb4a76.png) This change makes it so, instead of mixing string distance with type unification, function signature search works by mapping names to IDs at the start, reporting to the user any cases where it had to make corrections, and then matches with IDs when going through the items. This only changes function searches. Name searches are left alone, and corrections are only done when there's a single item in the search query.
Configuration menu - View commit details
-
Copy full SHA for fa8aeb1 - Browse repository at this point
Copy the full SHA fa8aeb1View commit details -
Rollup merge of rust-lang#110928 - loongarch-rs:tests, r=petrochenkov
tests: Add tests for LoongArch64
Configuration menu - View commit details
-
Copy full SHA for f135949 - Browse repository at this point
Copy the full SHA f135949View commit details -
Rollup merge of rust-lang#110970 - est31:test_dirs_relax, r=petrochenkov
tidy: remove ENTRY_LIMIT maximum checking and set it to 900 Removes checking of `ENTRY_LIMIT` towards an actually reached maximum, and sets it to 900. The number 900 is safely below github's limit of 1000 entries for a directory. PRs to move tests can still decrease the sizes of various directories, but adjusting the limit won't be neccessary any more. In fact, such reduction PRs are a great idea so that no unrelated PR is hitting the limit: ideally there would always be a (manually maintained) safety margin between the actually reached maximum and `ENTRY_LIMIT`, for all directories. In general, the limit is a bad tool to direct people to put tests into fitting directories because when those are available, usually the limit is not hit, while the limit is hit in directories that have a weak substructure themselves. I got into this situation myself when writing rust-lang#110694: tests/ui/parser is hitting the limit, but has few directories of its own. Suggested by ``@petrochenkov`` in rust-lang#110694 (comment). r? ``@petrochenkov``
Configuration menu - View commit details
-
Copy full SHA for 10e7825 - Browse repository at this point
Copy the full SHA 10e7825View commit details -
Rollup merge of rust-lang#111104 - Manishearth:icuup, r=compiler-errors
Update ICU4X to 1.2 Was released a couple weeks ago. Also needed to make progress on rust-lang#109302 (though this PR does not achieve that part just yet)
Configuration menu - View commit details
-
Copy full SHA for 8c53320 - Browse repository at this point
Copy the full SHA 8c53320View commit details -
Rollup merge of rust-lang#111127 - xfix:const-slice-flatten, r=scottmcm
Constify slice flatten method ACP: rust-lang/libs-team#218
Configuration menu - View commit details
-
Copy full SHA for 2986ec1 - Browse repository at this point
Copy the full SHA 2986ec1View commit details -
Rollup merge of rust-lang#111146 - petrochenkov:decident, r=compiler-…
…errors rustc_middle: Fix `opt_item_ident` for non-local def ids Noticed while working on rust-lang#110855.
Configuration menu - View commit details
-
Copy full SHA for 26d0790 - Browse repository at this point
Copy the full SHA 26d0790View commit details -
Rollup merge of rust-lang#111154 - djkoloski:use_builtin_ffx_isolatio…
…n, r=tmandry Use builtin FFX isolation for Fuchsia test runner FFX has new builtin support for isolating the daemon's environment. This switches the manual isolation originally written to that new builtin feature. r? ```@tmandry```
Configuration menu - View commit details
-
Copy full SHA for d66a026 - Browse repository at this point
Copy the full SHA d66a026View commit details