rust/compiler/rustc_codegen_cranelift/scripts/cargo.sh

#!/bin/bash

dir=$(dirname "$0")
source $dir/config.sh

# read nightly compiler from rust-toolchain file
TOOLCHAIN=$(cat $dir/rust-toolchain)

cmd=$1
shift || true

if [[ "$cmd" = "jit" ]]; then
cargo +${TOOLCHAIN} rustc "$@" -- --jit
else
cargo +${TOOLCHAIN} $cmd "$@"
fi
Test rust-lang/regex example shootout-regex-dna 2019-07-30 06:37:47 -05:00			`#!/bin/bash`

Refactor the build system 2020-11-02 11:16:57 -06:00			`dir=$(dirname "$0")`
			`source $dir/config.sh`
Store nightly snapshot in rust-toolchain file, and use it in cargo.sh The rust-toolchain file can also store an exact nightly snapshot (instead of just "nightly"), so we can store whatever snapshot that rustc_codegen_cranelift is known to work with. This also lets us add a new feature to `cargo.sh` to let it use the exact same nightly snapshot as cg_clif. If there's a nightly compiler mismatch, you get a confusing error message like: error: couldn't load codegen backend "librustc_codegen_cranelift.so": "librustc_driver-681e2b4f66c73d3e.so: cannot open shared object file: No such file or directory" So doing this automatically in cargo.sh is useful. 2020-01-15 11:05:18 -06:00
			`# read nightly compiler from rust-toolchain file`
Refactor the build system 2020-11-02 11:16:57 -06:00			`TOOLCHAIN=$(cat $dir/rust-toolchain)`
Test rust-lang/regex example shootout-regex-dna 2019-07-30 06:37:47 -05:00
			`cmd=$1`
Refactor the build system 2020-11-02 11:16:57 -06:00			`shift \|\| true`
Test rust-lang/regex example shootout-regex-dna 2019-07-30 06:37:47 -05:00
Replace CG_CLIF_JIT with --jit 2020-09-29 11:41:59 -05:00			`if [[ "$cmd" = "jit" ]]; then`
fix shellcheck error of SC2068 2020-11-02 06:17:52 -06:00			`cargo +${TOOLCHAIN} rustc "$@" -- --jit`
Replace CG_CLIF_JIT with --jit 2020-09-29 11:41:59 -05:00			`else`
fix shellcheck error of SC2068 2020-11-02 06:17:52 -06:00			`cargo +${TOOLCHAIN} $cmd "$@"`
Replace CG_CLIF_JIT with --jit 2020-09-29 11:41:59 -05:00			`fi`