rust/compiler/rustc_llvm/Cargo.toml

[package]
name = "rustc_llvm"
version = "0.0.0"
edition = "2021"

[features]
static-libstdcpp = []
emscripten = []

[dependencies]
libc = "0.2.73"

[build-dependencies]
cc = "1.0.69"
bootstrap: Add a bunch of Cargo.toml files These describe the structure of all our crate dependencies. 2016-01-21 17:19:23 -06:00			`[package]`
			`name = "rustc_llvm"`
			`version = "0.0.0"`
Migrate to 2021 2021-09-19 11:49:55 -05:00			`edition = "2021"`
bootstrap: Add a bunch of Cargo.toml files These describe the structure of all our crate dependencies. 2016-01-21 17:19:23 -06:00
			`[features]`
			`static-libstdcpp = []`
rustc: Split Emscripten to a separate codegen backend This commit introduces a separately compiled backend for Emscripten, avoiding compiling the `JSBackend` target in the main LLVM codegen backend. This builds on the foundation provided by #47671 to create a new codegen backend dedicated solely to Emscripten, removing the `JSBackend` of the main codegen backend in the process. A new field was added to each target for this commit which specifies the backend to use for translation, the default being `llvm` which is the main backend that we use. The Emscripten targets specify an `emscripten` backend instead of the main `llvm` one. There's a whole bunch of consequences of this change, but I'll try to enumerate them here: * A second LLVM submodule was added in this commit. The main LLVM submodule will soon start to drift from the Emscripten submodule, but currently they're both at the same revision. * Logic was added to rustbuild to not build the Emscripten backend by default. This is gated behind a `--enable-emscripten` flag to the configure script. By default users should neither check out the emscripten submodule nor compile it. * The `init_repo.sh` script was updated to fetch the Emscripten submodule from GitHub the same way we do the main LLVM submodule (a tarball fetch). * The Emscripten backend, turned off by default, is still turned on for a number of targets on CI. We'll only be shipping an Emscripten backend with Tier 1 platforms, though. All cross-compiled platforms will not be receiving an Emscripten backend yet. This commit means that when you download the `rustc` package in Rustup for Tier 1 platforms you'll be receiving two trans backends, one for Emscripten and one that's the general LLVM backend. If you never compile for Emscripten you'll never use the Emscripten backend, so we may update this one day to only download the Emscripten backend when you add the Emscripten target. For now though it's just an extra 10MB gzip'd. Closes #46819 2018-01-24 10:22:34 -06:00			`emscripten = []`
bootstrap: Add a bunch of Cargo.toml files These describe the structure of all our crate dependencies. 2016-01-21 17:19:23 -06:00
Fix weird implicit dependency between rustllvm and rustc_codegen_llvm rustllvm relies on the `LLVMRustStringWriteImpl` symbol existing, but this symbol was previously defined in a downstream crate (rustc_codegen_llvm, which depends on rustc_llvm. While this somehow worked under the old 'separate bootstrap step for codegen' scheme, it meant that rustc_llvm could not actually be built by itself, since it relied linking to the downstream rustc_codegen_llvm crate. Now that librustc_codegen_llvm is just a normal crate, we actually try to build a standalone rustc_llvm when we run tests. This commit moves `LLVMRustStringWriteImpl` into rustc_llvm (technically the rustllvm directory, which has its contents built by rustc_llvm). This ensures that we can build each crate in the graph by itself, without requiring that any downstream crates be linked in as well. 2019-12-12 09:51:19 -06:00			`[dependencies]`
Update dependencies that have knowledge about aarch64-apple-darwin 2020-07-11 13:52:30 -05:00			`libc = "0.2.73"`
Fix weird implicit dependency between rustllvm and rustc_codegen_llvm rustllvm relies on the `LLVMRustStringWriteImpl` symbol existing, but this symbol was previously defined in a downstream crate (rustc_codegen_llvm, which depends on rustc_llvm. While this somehow worked under the old 'separate bootstrap step for codegen' scheme, it meant that rustc_llvm could not actually be built by itself, since it relied linking to the downstream rustc_codegen_llvm crate. Now that librustc_codegen_llvm is just a normal crate, we actually try to build a standalone rustc_llvm when we run tests. This commit moves `LLVMRustStringWriteImpl` into rustc_llvm (technically the rustllvm directory, which has its contents built by rustc_llvm). This ensures that we can build each crate in the graph by itself, without requiring that any downstream crates be linked in as well. 2019-12-12 09:51:19 -06:00
bootstrap: Add a bunch of Cargo.toml files These describe the structure of all our crate dependencies. 2016-01-21 17:19:23 -06:00			`[build-dependencies]`
Upgrade `cc` crate to 1.0.69 2021-07-13 03:58:50 -05:00			`cc = "1.0.69"`