Alex Crichton 40ef6cb749 Allow FFI-unsafe warnings for u128/i128 (#323) ... * Allow FFI-unsafe warnings for u128/i128 Handle new warnings on nightly, and we shouldn't need to worry about these with compiler-builtins since this is tied to a particular compiler. * Clean up crate attributes * No need for stability marker * Rustdoc docs not used for this crate * Remove old build-system related cruft from rustc itself. * Run `cargo fmt`		2019-11-11 12:19:10 -06:00
..
float	Remove the need for #[cfg] in #[use_c_shim_if]	2019-05-15 12:59:31 -07:00
int	Replace {u,i}128_* lang items with __rust_{u,i}128_* unmangled functions	2019-07-13 11:38:35 +02:00
arm.rs	remove unused imports	2019-07-13 11:00:15 +02:00
arm_linux.rs	Run rustfmt over everything	2019-05-14 14:40:38 -07:00
lib.rs	Allow FFI-unsafe warnings for u128/i128 (#323)	2019-11-11 12:19:10 -06:00
macros.rs	Replace {u,i}128_* lang items with __rust_{u,i}128_* unmangled functions	2019-07-13 11:38:35 +02:00
math.rs	Update libm for fmin/fmax/fminf/fmaxf	2019-06-05 23:41:18 +01:00
mem.rs	Implement bcmp (#315)	2019-09-30 11:02:47 -05:00
probestack.rs	probestack: add frame pointers for easier traceback	2019-07-24 10:18:30 +03:00
riscv32.rs	Fix compile on riscv again	2018-08-31 16:00:12 -07:00
x86.rs	Add "volatile" and "memory" clobber to asm! that doesn't fall through.	2017-11-15 12:49:10 -08:00
x86_64.rs	Emit `_fltused` on `uefi` targets as a short-term workaround (#317)	2019-11-07 13:04:11 -06:00