Mark Rousskov 389b7ff190 Do not link LLVM tools to LLVM dylib unless rustc is ... Previously we would have some platforms where LLVM was linked to rustc statically, but to the LLVM tools dynamically. That meant we were distributing two copies of LLVM: one as a separate dylib and one statically linked in to librustc_driver.		2020-09-19 18:21:08 -04:00
..
azure-pipelines	Make sure we build target-only things (e.g., docs) for host platforms too	2020-09-18 12:00:53 -04:00
docker	Auto merge of #76420 - Gelbpunkt:aarch64-linux-musl, r=pietroalbini	2020-09-16 17:22:54 +00:00
github-actions	Make sure we build target-only things (e.g., docs) for host platforms too	2020-09-18 12:00:53 -04:00
scripts	ci: avoid moving the build directory on GHA	2020-09-10 12:54:29 +02:00
cpu-usage-over-time.py	remove unnecessary semicolons	2020-02-07 23:35:27 -05:00
init_repo.sh	Remove src/llvm-emscripten submodule	2019-10-21 13:05:31 -07:00
publish_toolstate.sh	more toolstate comments	2020-03-04 08:30:26 -08:00
run.sh	Do not link LLVM tools to LLVM dylib unless rustc is	2020-09-19 18:21:08 -04:00
shared.sh	ci: avoid symlinking the build directory on self-hosted builders	2020-07-23 11:29:47 +02:00