rust/src/librustc_trans/Cargo.toml

[package]
authors = ["The Rust Project Developers"]
name = "rustc_trans"
version = "0.0.0"

[lib]
name = "rustc_trans"
path = "lib.rs"
crate-type = ["dylib"]
test = false

[dependencies]
flate = { path = "../libflate" }
log = "0.3"
rustc = { path = "../librustc" }
rustc_back = { path = "../librustc_back" }
rustc_bitflags = { path = "../librustc_bitflags" }
rustc_const_math = { path = "../librustc_const_math" }
rustc_data_structures = { path = "../librustc_data_structures" }
rustc_errors = { path = "../librustc_errors" }
rustc_incremental = { path = "../librustc_incremental" }
rustc_llvm = { path = "../librustc_llvm" }
rustc_platform_intrinsics = { path = "../librustc_platform_intrinsics" }
serialize = { path = "../libserialize" }
syntax = { path = "../libsyntax" }
syntax_pos = { path = "../libsyntax_pos" }
bootstrap: Add a bunch of Cargo.toml files These describe the structure of all our crate dependencies. 2016-01-21 15:19:23 -08:00			`[package]`
			`authors = ["The Rust Project Developers"]`
			`name = "rustc_trans"`
			`version = "0.0.0"`

			`[lib]`
			`name = "rustc_trans"`
			`path = "lib.rs"`
			`crate-type = ["dylib"]`
rustbuild: Add support for crate tests + doctests This commit adds support to rustbuild to run crate unit tests (those defined by `#[test]`) as well as documentation tests. All tests are powered by `cargo test` under the hood. Each step requires the `libtest` library is built for that corresponding stage. Ideally the `test` crate would be a dev-dependency, but for now it's just easier to ensure that we sequence everything in the right order. Currently no filtering is implemented, so there's not actually a method of testing only libstd or only libcore, but rather entire swaths of crates are tested all at once. A few points of note here are: * The `coretest` and `collectionstest` crates are just listed as `[[test]]` entires for `cargo test` to naturally pick up. This mean that `cargo test -p core` actually runs all the tests for libcore. * Libraries that aren't tested all mention `test = false` in their `Cargo.toml` * Crates aren't currently allowed to have dev-dependencies due to rust-lang/cargo#860, but we can likely alleviate this restriction once workspaces are implemented. cc #31590 2016-04-29 14:23:15 -07:00			`test = false`
bootstrap: Add a bunch of Cargo.toml files These describe the structure of all our crate dependencies. 2016-01-21 15:19:23 -08:00
			`[dependencies]`
			`flate = { path = "../libflate" }`
Remove internal liblog This commit deletes the internal liblog in favor of the implementation that lives on crates.io. Similarly it's also setting a convention for adding crates to the compiler. The main restriction right now is that we want compiler implementation details to be unreachable from normal Rust code (e.g. requires a feature), and by default everything in the sysroot is reachable via `extern crate`. The proposal here is to require that crates pulled in have these lines in their `src/lib.rs`: #![cfg_attr(rustbuild, feature(staged_api, rustc_private))] #![cfg_attr(rustbuild, unstable(feature = "rustc_private", issue = "27812"))] This'll mean that by default they're not using these attributes but when compiled as part of the compiler they do a few things: * Mark themselves as entirely unstable via the `staged_api` feature and the `#![unstable]` attribute. * Allow usage of other unstable crates via `feature(rustc_private)` which is required if the crate relies on any other crates to compile (other than std). 2017-02-15 07:57:59 -08:00			`log = "0.3"`
bootstrap: Add a bunch of Cargo.toml files These describe the structure of all our crate dependencies. 2016-01-21 15:19:23 -08:00			`rustc = { path = "../librustc" }`
			`rustc_back = { path = "../librustc_back" }`
Use llvm::Attribute API instead of "raw value" APIs, which will be removed in LLVM 4.0. The librustc_llvm API remains mostly unchanged, except that llvm::Attribute is no longer a bitflag but represents only a single attribute. The ability to store many attributes in a small number of bits and modify them without interacting with LLVM is only used in rustc_trans::abi and closely related modules, and only attributes for function arguments are considered there. Thus rustc_trans::abi now has its own bit-packed representation of argument attributes, which are translated to rustc_llvm::Attribute when applying the attributes. 2016-11-16 23:36:08 +01:00			`rustc_bitflags = { path = "../librustc_bitflags" }`
rename `rustc_const_eval` to `rustc_const_math` 2016-03-15 12:33:13 +01:00			`rustc_const_math = { path = "../librustc_const_math" }`
bootstrap: Add a bunch of Cargo.toml files These describe the structure of all our crate dependencies. 2016-01-21 15:19:23 -08:00			`rustc_data_structures = { path = "../librustc_data_structures" }`
Move errors from libsyntax to its own crate 2016-06-21 18:08:13 -04:00			`rustc_errors = { path = "../librustc_errors" }`
make an incremental crate for now, this houses `svh` and the code to check `assert_dep_graph` is sane 2016-03-28 17:36:56 -04:00			`rustc_incremental = { path = "../librustc_incremental" }`
bootstrap: Add a bunch of Cargo.toml files These describe the structure of all our crate dependencies. 2016-01-21 15:19:23 -08:00			`rustc_llvm = { path = "../librustc_llvm" }`
			`rustc_platform_intrinsics = { path = "../librustc_platform_intrinsics" }`
Add Emscripten-specific linker It claims to accept most GNU linker options, but in fact most of them have no effect and instead it requires some special options which are easier to handle in a separate trait. Currently added: - `export_symbols`: works on executables as special Emscripten case since staticlibs/dylibs aren't compiled to JS, while exports are required to be accessible from JS. Fixes #39171. - `optimize` - translates Rust's optimization level to Emscripten optimization level (whether passed via `-C opt-level=...` or `-O...`). Fixes #36899. - `debuginfo` - translates debug info; Emscripten has 5 debug levels while Rust has 3, so chose to translate `-C debuginfo=1` to `-g3` (preserves whitespace, variable and function names for easy debugging). Fixes #36901. - `no_default_libraries` - tells Emscripten to exlude `memcpy` and co. 2017-02-03 14:58:13 +00:00			`serialize = { path = "../libserialize" }`
bootstrap: Add a bunch of Cargo.toml files These describe the structure of all our crate dependencies. 2016-01-21 15:19:23 -08:00			`syntax = { path = "../libsyntax" }`
Such large. Very 128. Much bits. This commit introduces 128-bit integers. Stage 2 builds and produces a working compiler which understands and supports 128-bit integers throughout. The general strategy used is to have rustc_i128 module which provides aliases for iu128, equal to iu64 in stage9 and iu128 later. Since nowhere in rustc we rely on large numbers being supported, this strategy is good enough to get past the first bootstrap stages to end up with a fully working 128-bit capable compiler. In order for this strategy to work, number of locations had to be changed to use associated max_value/min_value instead of MAX/MIN constants as well as the min_value (or was it max_value?) had to be changed to use xor instead of shift so both 64-bit and 128-bit based consteval works (former not necessarily producing the right results in stage1). This commit includes manual merge conflict resolution changes from a rebase by @est31. 2016-08-23 03:56:52 +03:00			`syntax_pos = { path = "../libsyntax_pos" }`