rust/src/test/codegen, branch 1.54.0

Revert "Allow specifying alignment for functions"

2021-06-19T14:27:44+00:00

This reverts commit 448d07683a6defd567996114793a09c9a8aef5df.

Auto merge of #79608 - alessandrod:bpf, r=nagisa

2021-06-06T01:02:32+00:00

BPF target support This adds `bpfel-unknown-none` and `bpfeb-unknown-none`, two new no_std targets that generate little and big endian BPF. The approach taken is very similar to the cuda target, where `TargetOptions::obj_is_bitcode` is enabled and code generation is done by the linker. I added the targets to `dist-various-2`. There are [some tests](https://github.com/alessandrod/bpf-linker/tree/main/tests/assembly) in bpf-linker and I'm planning to add more. Those are currently not ran as part of rust CI.

Update generator tests

2021-06-02T20:09:23+00:00

BPF: remove unnecessary flags from src/test/codegen/bpf-alu32.rs

2021-05-30T01:50:43+00:00

BPF: fix #[target_feature(enable = "alu32")]

2021-05-29T12:23:32+00:00

Auto merge of #84876 - alexcrichton:inline-thread-locals-cross-crate, r=Mark-Simulacrum

2021-05-19T15:59:46+00:00

std: Attempt again to inline thread-local-init across crates Issue #25088 has been part of `thread_local!` for quite some time now. Historical attempts have been made to add `#[inline]` to `__getit` in #43931, #50252, and #59720, but these attempts ended up not landing at the time due to segfaults on Windows. In the interim though with `const`-initialized thread locals AFAIK this is the only remaining bug which is why you might want to use `#[thread_local]` over `thread_local!`. As a result I figured it was time to resubmit this and see how it fares on CI and if I can help debugging any issues that crop up. Closes #25088

Auto merge of #84767 - scottmcm:try_trait_actual, r=lcnr

2021-05-18T20:50:01+00:00

Implement the new desugaring from `try_trait_v2` ~~Currently blocked on https://github.com/rust-lang/rust/issues/84782, which has a PR in https://github.com/rust-lang/rust/pull/84811~~ Rebased atop that fix. `try_trait_v2` tracking issue: https://github.com/rust-lang/rust/issues/84277 Unfortunately this is already touching a ton of things, so if you have suggestions for good ways to split it up, I'd be happy to hear them. (The combination between the use in the library, the compiler changes, the corresponding diagnostic differences, even MIR tests mean that I don't really have a great plan for it other than trying to have decently-readable commits. r? `@ghost` ~~(This probably shouldn't go in during the last week before the fork anyway.)~~ Fork happened.

No matter how trivial the change, tidy always finds a way to complain...

2021-05-18T18:48:00+00:00

Mention the issue number for the new mir-opt in the FIXMEs

2021-05-18T18:29:34+00:00

Thanks for the suggestions, lcnr! Co-authored-by: lcnr

std: Attempt again to inline thread-local-init across crates

2021-05-18T18:22:04+00:00

Issue #25088 has been part of `thread_local!` for quite some time now. Historical attempts have been made to add `#[inline]` to `__getit` in #43931, #50252, and #59720, but these attempts ended up not landing at the time due to segfaults on Windows. In the interim though with `const`-initialized thread locals AFAIK this is the only remaining bug which is why you might want to use `#[thread_local]` over `thread_local!`. As a result I figured it was time to resubmit this and see how it fares on CI and if I can help debugging any issues that crop up. Closes #25088