rust/src/librustc_const_math/Cargo.toml

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

[lib]
name = "rustc_const_math"
path = "lib.rs"
crate-type = ["dylib"]

[dependencies]
serialize = { path = "../libserialize" }
syntax = { path = "../libsyntax" }
rustc_i128 = { path = "../librustc_i128" }
rustbuild 2016-03-14 09:29:18 +01:00			`[package]`
			`authors = ["The Rust Project Developers"]`
rename `rustc_const_eval` to `rustc_const_math` 2016-03-15 12:33:13 +01:00			`name = "rustc_const_math"`
rustbuild 2016-03-14 09:29:18 +01:00			`version = "0.0.0"`

			`[lib]`
rename `rustc_const_eval` to `rustc_const_math` 2016-03-15 12:33:13 +01:00			`name = "rustc_const_math"`
rustbuild 2016-03-14 09:29:18 +01:00			`path = "lib.rs"`
			`crate-type = ["dylib"]`

			`[dependencies]`
			`serialize = { path = "../libserialize" }`
			`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			`rustc_i128 = { path = "../librustc_i128" }`