diff options
| author | Guillaume Gomez <guillaume1.gomez@gmail.com> | 2024-05-02 15:11:23 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-05-02 15:11:23 +0200 |
| commit | 1b0972cc619d6c00d96bda0eb84708a14c1f1250 (patch) | |
| tree | c4f5f071329a9df750c549b7753a8f5f05a0abd8 /compiler/rustc_codegen_ssa/src/errors.rs | |
| parent | 871f047c4cdfda748e8490c7d35c041b875d2026 (diff) | |
| parent | 393d9334d986a21ab1c7a6c4fe0c5f4f550aa3cc (diff) | |
| download | rust-1b0972cc619d6c00d96bda0eb84708a14c1f1250.tar.gz rust-1b0972cc619d6c00d96bda0eb84708a14c1f1250.zip | |
Rollup merge of #124597 - cuviper:x86-64-v3, r=workingjubilee
Use an explicit x86-64 cpu in tests that are sensitive to it 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.
Diffstat (limited to 'compiler/rustc_codegen_ssa/src/errors.rs')
0 files changed, 0 insertions, 0 deletions
