fork/rust
git clone https://git.julia.blue/fork/rust
49cae55760d
1.44.0
1FROM ubuntu:18.04 2 3RUN apt-get update && apt-get install -y --no-install-recommends \ 4 g++ \ 5 g++-arm-linux-gnueabi \ 6 make \ 7 file \ 8 curl \ 9 ca-certificates \ 10 python2.7 \ 11 git \ 12 cmake \ 13 sudo \ 14 gdb \ 15 llvm-8-tools \ 16 libedit-dev \ 17 libssl-dev \ 18 pkg-config \ 19 zlib1g-dev \ 20 xz-utils \ 21 nodejs 22 23COPY scripts/sccache.sh /scripts/ 24RUN sh /scripts/sccache.sh 25 26# using llvm-link-shared due to libffi issues -- see #34486 27ENV RUST_CONFIGURE_ARGS \ 28 --build=x86_64-unknown-linux-gnu \ 29 --llvm-root=/usr/lib/llvm-8 \ 30 --enable-llvm-link-shared \ 31 --set rust.thin-lto-import-instr-limit=10 32 33ENV SCRIPT python2.7 ../x.py test --exclude src/tools/tidy && \ 34 # Run the `mir-opt` tests again but this time for a 32-bit target. 35 # This enforces that tests using `// EMIT_MIR_FOR_EACH_BIT_WIDTH` have 36 # both 32-bit and 64-bit outputs updated by the PR author, before 37 # the PR is approved and tested for merging. 38 # It will also detect tests lacking `// EMIT_MIR_FOR_EACH_BIT_WIDTH`, 39 # despite having different output on 32-bit vs 64-bit targets. 40 # 41 # HACK(eddyb) `armv5te` is used (not `i686`) to support older LLVM than LLVM 9: 42 # https://github.com/rust-lang/compiler-builtins/pull/311#issuecomment-612270089. 43 # This also requires `--pass=build` because we can't execute the tests 44 # on the `x86_64` host when they're built as `armv5te` binaries. 45 # (we're only interested in the MIR output, so this doesn't matter) 46 python2.7 ../x.py test src/test/mir-opt --pass=build \ 47 --target=armv5te-unknown-linux-gnueabi && \ 48 # Run tidy at the very end, after all the other tests. 49 python2.7 ../x.py test src/tools/tidy 50 51# The purpose of this container isn't to test with debug assertions and 52# this is run on all PRs, so let's get speedier builds by disabling these extra 53# checks. 54ENV NO_DEBUG_ASSERTIONS=1 55ENV NO_LLVM_ASSERTIONS=1