rust/tests/codegen/target-feature-inline-closure.rs, branch 1.83.0 https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.83.0 2024-05-01T23:54:20+00:00 Add inline comments why we're forcing the target cpu 2024-05-01T23:54:20+00:00 Josh Stone jistone@redhat.com 2024-05-01T23:54:20+00:00 urn:sha1:1b79bb937f399e82768ea90fb0d0b4ffd5a915d4 Use an explicit x86-64 cpu in tests that are sensitive to it 2024-05-01T22:25:26+00:00 Josh Stone jistone@redhat.com 2024-05-01T22:25:26+00:00 urn:sha1:706f06c39a9e08a4708a53722429d13ae4069c2f There are a few tests that depend on some target features **not** being enabled by default, and usually they are correct with the default x86-64 target CPU. However, in downstream builds we have modified the default to fit our distros -- `x86-64-v2` in RHEL 9 and `x86-64-v3` in RHEL 10 -- and the latter especially trips tests that expect not to have AVX. These cases are few enough that we can just set them back explicitly. [AUTO_GENERATED] Migrate compiletest to use `ui_test`-style `//@` directives 2024-02-22T16:04:04+00:00 许杰友 Jieyou Xu (Joe) jieyouxu@outlook.com 2024-02-22T12:10:29+00:00 urn:sha1:6e48b96692d63a79a14563f27fe5185f122434f8 Don't accidentally detect the commit hash as an `fadd` instruction 2023-10-10T05:59:49+00:00 Zalathar Zalathar@users.noreply.github.com 2023-10-10T05:59:49+00:00 urn:sha1:58d62fc271457a5d1cfdfc947c5039df6326a45e Add codegen test ensuring always-inline closures don't bypass target features 2023-07-17T01:26:08+00:00 Caleb Zulawski caleb.zulawski@gmail.com 2023-07-17T01:25:46+00:00 urn:sha1:cdb9de7e8bd70c7e3580ec28b37af879e555f45d