about summary refs log tree commit diff
path: root/library/stdarch/ci/docker
AgeCommit message (Collapse)AuthorLines
2020-03-29Install Python3 to wasm32 CI since wabt removes Python2 support (#840)Makoto Kato-0/+1
See https://github.com/WebAssembly/wabt/pull/1321
2019-10-26ci: switch mirrors to use our CDNPietro Albini-2/+2
We recently added a CDN in front of our CI mirrors as it's faster and cheaper for us. This switches libc's CI to use it instead of accessing the underlying bucket directly.
2019-05-13Unbreak powerpc64 CILuca Barbato-1/+1
2019-05-13Unbreak powerpc64le CILuca Barbato-1/+2
2019-05-09Update Intel SDE and enable RTM full emulationgnzlbg-3/+3
2019-04-25Download node binariesAlex Crichton-17/+3
2019-04-25Hook tests up to node.jsAlex Crichton-8/+34
We can even test some of the functions!
2019-02-23Unify PPC DockerfilesMateusz Mikuła-12/+5
2019-02-23Upgrade EOL docker images to Ubuntu 18.04Mateusz Mikuła-13/+13
2019-02-13Fix nvptx64 libcore-only build on travis.Peter Jin-0/+0
2018-12-29Add a build libcore-only nvptx64 test (using xargo).Peter Jin-0/+5
This also disables the "integer_atomics" feature on nvptx/nvptx64.
2018-11-11remove intel_sde featuregnzlbg-1/+0
2018-11-11add mips docker containersgnzlbg-0/+58
2018-09-17Remove lld-shim.rs no longer needed on wasmAlex Crichton-10/+0
Bugs are fixed upstream!
2018-09-06Rename `wasm32` memory intrinsics (#560)Alex Crichton-2/+2
The official name of the memory intrinsics has changed to `memory.size` and `memory.grow`, so let's reflect that with our naming as well! Additionally they have an argument of which memory to operate on with LLVM and must always be zero currently.
2018-08-15Add wasm32 simd128 intrinsics (#549)gnzlbg-0/+37
* 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-26[s390x] add CIgnzlbg-0/+13
This commit tests `s390x-unknown-linux-gnu` on CI using `qemu-user`. Closes #499 .
2018-06-23add CI for Androidgnzlbg-0/+123
2018-05-16Initial PowerPC altivec and VSX support (#447)gnzlbg-1/+1
* add some powerpc/powerpc64 altivec/vsx intrinsics * temporarily make IntoBits/FromBits inline(always) * include powerpc64 module; use inline(always) from/into_bits only on powerpc
2018-04-26fix errors/warnings from the stabilization of cfg_target_feature and ↵gnzlbg-0/+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
2018-04-03update ubuntu versiongnzlbg-1/+1
2018-04-03update intel SDE versiongnzlbg-3/+3
2018-01-18Migrate the `i586::avx` module to vendor types (#286)Alex Crichton-4/+4
Closes #285
2017-12-14[ci] powerpc/powerpc64/powerpc64le (#237)gnzlbg-0/+40
* [ci] add powerpc/powerpc64 build bots * unbreak stdsimd builds for targets without run-time
2017-11-22Add FXSAVE/FXRSTOR, update Intel SDE, fix xsave tests (#205)gnzlbg-4/+4
* [x86] add run-time detection for fxsr * [x86] add i386 fxsr intrinsics: FXSAVE,FXRSTOR * [x86_64] add x86_64 fxsr intrinsics: FXSAVE64/FXRSTOR64 * [x86-runtime]: document xsave detection further * [x86] disable xsaves and xsaves64 tests
2017-11-17[arm] runtime-detection supportgnzlbg-0/+1
2017-10-18Add CI in Intel's instruction emulator (#113)Alex Crichton-0/+13
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-10-06Add an i586 builder (#101)Alex Crichton-0/+7
The i586 targets on x86 are defined to be 32-bit and lacking in sse/sse2 unlike the i686 target which has sse2 turned on by default. I was mostly curious what would happen when turning on this target, and it turns out quite a few tests failed! Most of the tests here had to do with calling functions with ABI mismatches where the callee wasn't `#[inline(always)]`. Various pieces have been updated now and we should be passing all tests. Only one instruction assertion ended up changing where the function generates a different instruction with sse2 ambiently enabled and without it enabled.
2017-09-21Add CI for more platformsAlex Crichton-0/+53
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.