about summary refs log tree commit diff
path: root/library/stdarch/ci/run-docker.sh
AgeCommit message (Collapse)AuthorLines
2025-07-22Remove `std_detect` from stdarch's CIJakub Beránek-1/+0
2025-05-30Add back `std_detect_env_override`sayantn-0/+1
2025-05-03fix - aarch64_be testsJames Barford-Evans-0/+1
2025-04-23reset the host linkerFolkert de Vries-0/+6
The host's linker is used to compile build.rs files (e.g. for libc). When the user configures a custom liker (e.g. mold) in their own .cargo/config.toml or ~/.cargo/config.toml, that linker will likely not work when running run-docker.sh. So, we now reset it to `cc`, which should always be installed in the docker container.
2025-04-23run `cargo generate-lockfile` before running dockerFolkert de Vries-0/+3
2025-04-20Augment `stdarch-test` to parse PPCsayantn-2/+0
- Remove some unused env variables from `run.sh`
2025-04-20Remove `x86_64-unknown-linux-gnu` runsayantn-2/+1
+ Rename `x86_64-unknown-linux-gnu-emulated` run to `x86_64-unknown-linux-gnu`
2023-09-01Impr: Add a usage check for the ci/run-docker.sh scriptGijs Burghoorn-0/+5
2021-12-04Update the intrinsic checker tool (#1258)Amanieu d'Antras-1/+1
2021-09-09Intrinsic test tool to compare neon intrinsics with C (#1170)Jamie Cunliffe-1/+3
2019-07-14Add Azure Pipelinesgnzlbg-7/+7
2019-07-09Update repo namegnzlbg-6/+6
2019-02-13Use builtin nvptx64-nvidia-cuda targetgnzlbg-14/+3
2018-12-29Add a build libcore-only nvptx64 test (using xargo).Peter Jin-4/+15
This also disables the "integer_atomics" feature on nvptx/nvptx64.
2018-11-11silence shellcheck warninggnzlbg-0/+1
2018-11-11pass RUSTFLAGS to dockergnzlbg-0/+1
2018-11-11fix clippy and shellcheck issuesgnzlbg-11/+13
2018-11-11cleanup travis and run.sh scriptsgnzlbg-0/+4
2018-08-15Add wasm32 simd128 intrinsics (#549)gnzlbg-3/+3
* Add wasm32 simd128 intrinsics * test wasm32 simd128 instructions * Run wasm tests like all other tests * use modules instead of types to access wasm simd128 interpretations * generate docs for wasm32-unknown-unknown * fix typo * Enable #[assert_instr] on wasm32 * Shell out to Node's `execSync` to execute `wasm2wat` over our wasm file * Parse the wasm file line-by-line, looking for various function markers and such * Use the `elem` section to build a function pointer table, allowing us to map exactly from function pointer to a function * Avoid losing debug info (the names section) in release mode by stripping `--strip-debug` from `rust-lld`. * remove exclude list from Cargo.toml * fix assert_instr for non-wasm targets * re-format assert-instr changes * add crate that uses assert_instr * Fix instructions having extra quotes * Add assert_instr for wasm memory intrinsics * Remove hacks for git wasm-bindgen * add wasm_simd128 feature * make wasm32 build correctly * run simd128 tests on ci * remove wasm-assert-instr-tests
2018-06-23add CI for Androidgnzlbg-1/+2
2018-04-26fix errors/warnings from the stabilization of cfg_target_feature and ↵gnzlbg-2/+1
target_feature (#432) * fix build after stabilization of cfg_target_feature and target_feature * fix doc tests * fix spurious unused_attributes warning * fix more unused attribute warnings * More unnecessary target features * Remove no longer needed trait imports * Remove fixed upstream workarounds * Fix parsing the #[assert_instr] macro Following upstream proc_macro changes * Fix form and parsing of #[simd_test] * Don't use Cargo features for testing modes Instead use RUSTFLAGS with `--cfg`. This'll help us be compatible with the latest Cargo where a tweak to workspaces and features made the previous invocations we had invalid. * Don't thread RUSTFLAGS through docker * Re-gate on x86 verification Closes #411
2017-11-22Use workspaces and fix testsAlex Crichton-1/+1
* Enable a Cargo workspace for the repo * Disable tests for proc-macro crates * Move back to mounting source directory read-only * Refactor test invocation to only test one crate with `--all`
2017-11-22refactor no_std components into the coresimd crategnzlbg-1/+1
2017-11-17[arm] runtime-detection supportgnzlbg-1/+2
2017-11-17[ci] add intel_sde featuregnzlbg-1/+2
2017-10-18Add CI in Intel's instruction emulator (#113)Alex Crichton-2/+5
This commit adds a new builder on CI for running tests in Intel's own emulator and also adds an assertion that on this emulator no tests are skipped due to missing CPU features by accident. Closes #92
2017-09-21Add CI for more platformsAlex Crichton-0/+32
This commit adds CI for a few more targets: * i686-unknown-linux-gnu * arm-unknown-linux-gnueabihf * armv7-unknown-linux-gnueabihf * aarch64-unknown-linux-gnu The CI here is structured around using a Docker container to set up a test environment and then QEMU is used to actually execute code from these platforms. QEMU's emulation actually makes it so we can continue to just use `cargo test`, as processes can be spawned from QEMU like `objdump` and files can be read (for libbacktrace). Ends up being a relatively seamless experience! Note that a number of intrinsics were disabled on i686 because they were failing tests, and otherwise a few ARM touch-ups were made to get tests passing.