-
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 11 pull requests #127665
Rollup of 11 pull requests #127665
Conversation
Since the libs and lang teams completed an FCP to allow for const `strlen` ([1]), currently implemented with `const_eval_select`, there is no longer any reason to avoid this specific function or use it only in const. Rename it to reflect this status change. [1]: rust-lang#113219 (comment)
…es, r=estebank Ignore allocation bytes in some mir-opt tests This adds `rustc -Zdump-mir-exclude-alloc-bytes` to skip writing allocation bytes in MIR dumps, and applies it to tests that were failing on s390x due to its big-endian byte order. Fixes rust-lang#126261
…estebank add lint for inline asm labels that look like binary fixes rust-lang#94426 Due to a bug/feature in LLVM, labels composed of only the digits `0` and `1` can sometimes be confused with binary literals, even if a binary literal would not be valid in that position. This PR adds detection for such labels and also as a drive-by change, adds a note to cases such as `asm!(include_str!("file"))` that the label that it found came from an expansion of a macro, it wasn't found in the source code. I expect this PR to upset some people that were using labels `0:` or `1:` without issue because they never hit the case where LLVM got it wrong, but adding a heuristic to the lint to prevent this is not feasible - it would involve writing a whole assembly parser for every target that we have assembly support for. [zulip discussion](https://rust-lang.zulipchat.com/#narrow/stream/238009-t-compiler.2Fmeetings/topic/.5Bweekly.5D.202024-06-20/near/445870628) r? ``@estebank``
Added the `xop` target-feature and the `xop_target_feature` feature gate This is an effort towards rust-lang#127208. This adds the `xop` target feature gated by `xop_target_feature`.
…rt-ice, r=estebank Fix import suggestion ice Fixes rust-lang#127302 rust-lang#127302 only crash in edition 2015 rust-lang#120074 can only reproduced in edition 2021 so I added revisions in test file.
…jieyouxu Migrate `extra-filename-with-temp-outputs` and `issue-85019-moved-src-dir` `run-make` tests to rmake Part of rust-lang#121876 and the associated [Google Summer of Code project](https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html). Please try: try-job: armhf-gnu // try-job: test-various // already tried try-job: x86_64-msvc try-job: aarch64-apple
…=jieyouxu Migrate `issue-83045`, `rustc-macro-dep-files` and `env-dep-info` `run-make` tests to rmake Part of rust-lang#121876 and the associated [Google Summer of Code project](https://blog.rust-lang.org/2024/05/01/gsoc-2024-selected-projects.html). Please try on musl. try-job: dist-x86_64-musl
…rn_blocks, r=oli-obk Fire unsafe_code lint on unsafe extern blocks Fixes rust-lang#126738
…better-sugg, r=oli-obk Suggest using precise capturing for hidden type that captures region Adjusts the "add `+ '_`" suggestion for opaques to instead suggest adding or reusing the `+ use<>` in the opaque. r? oli-obk or please re-roll if you're busy!
…=lcnr Remove `fully_normalize` Yeet this function and replace it w/ some `ObligationCtxt` instead. It wasn't called very often anyways. r? lcnr
…rustdoc, r=fmease Implement `precise_capturing` support for rustdoc Implements rustdoc (+json) support for local (i.e. non-cross-crate-inlined) RPITs with `use<...>` precise capturing syntax. Tests kinda suck. They're really hard to write 😰 r? `@fmease` or re-roll if you're too busy! also cc `@aDotInTheVoid` for the json side Tracking: * rust-lang#127228 (comment) (not fully fixed for cross-crate-inlined opaques) * rust-lang#123432
…olnay Rename the internal `const_strlen` to just `strlen` Since the libs and lang teams completed an FCP to allow for const `strlen` ([1]), currently implemented with `const_eval_select`, there is no longer any reason to avoid this specific function or use it only in const. Rename it to reflect this status change. [1]: rust-lang#113219 (comment)
@bors r+ rollup=never p=11 |
☀️ Test successful - checks-actions |
📌 Perf builds for each rolled up PR:
previous master: c6727fc9b5 In the case of a perf regression, run the following command for each PR you suspect might be the cause: |
Finished benchmarking commit (336e89b): comparison URL. Overall result: ❌ regressions - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesResults (secondary 4.5%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 705.609s -> 704.601s (-0.14%) |
Successful merges:
xop
target-feature and thexop_target_feature
feature gate #127209 (Added thexop
target-feature and thexop_target_feature
feature gate)extra-filename-with-temp-outputs
andissue-85019-moved-src-dir
run-make
tests to rmake #127338 (Migrateextra-filename-with-temp-outputs
andissue-85019-moved-src-dir
run-make
tests to rmake)issue-83045
,rustc-macro-dep-files
andenv-dep-info
run-make
tests to rmake #127381 (Migrateissue-83045
,rustc-macro-dep-files
andenv-dep-info
run-make
tests to rmake)fully_normalize
#127631 (Removefully_normalize
)precise_capturing
support for rustdoc #127632 (Implementprecise_capturing
support for rustdoc)const_strlen
to juststrlen
#127660 (Rename the internalconst_strlen
to juststrlen
)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup