Add ARM targets to CI
Specifically `aarch64-unknown-linux-gnu` and `arm-unknown-linux-gnueabi`
This commit is contained in:
parent
d4d7edfdf3
commit
04b2aab141
@ -213,7 +213,9 @@ degree documented below):
|
||||
- The best-supported target is `x86_64-unknown-linux-gnu`. Miri releases are
|
||||
blocked on things working with this target. Most other Linux targets should
|
||||
also work well; we do run the test suite on `i686-unknown-linux-gnu` as a
|
||||
32bit target and `mips64-unknown-linux-gnuabi64` as a big-endian target.
|
||||
32bit target and `mips64-unknown-linux-gnuabi64` as a big-endian target, as
|
||||
well as the ARM targets `aarch64-unknown-linux-gnu` and
|
||||
`arm-unknown-linux-gnueabi`.
|
||||
- `x86_64-apple-darwin` should work basically as well as Linux. We also test
|
||||
`aarch64-apple-darwin`. However, we might ship Miri with a nightly even when
|
||||
some features on these targets regress.
|
||||
|
@ -104,6 +104,8 @@ run_tests
|
||||
case $HOST_TARGET in
|
||||
x86_64-unknown-linux-gnu)
|
||||
MIRI_TEST_TARGET=i686-unknown-linux-gnu run_tests
|
||||
MIRI_TEST_TARGET=aarch64-unknown-linux-gnu run_tests
|
||||
MIRI_TEST_TARGET=arm-unknown-linux-gnueabi run_tests
|
||||
MIRI_TEST_TARGET=aarch64-apple-darwin run_tests
|
||||
MIRI_TEST_TARGET=i686-pc-windows-msvc run_tests
|
||||
MIRI_TEST_TARGET=x86_64-unknown-freebsd run_tests_minimal hello integer vec panic/panic concurrency/simple atomic data_race env/var
|
||||
|
Loading…
x
Reference in New Issue
Block a user