Corey Richardson 2dc2ac1e6b liblibc: don't use int/uint for intptr_t/uintptr_t ... int/uint aren't considered FFI safe, replace them with the actual type they represent (i64/u64 or i32/u32). This is a breaking change, but at most a cast to `uint` or `int` needs to be added. [breaking-change]		2014-08-20 21:02:24 -04:00
..
auxiliary	liblibc: don't use int/uint for intptr_t/uintptr_t	2014-08-20 21:02:24 -04:00
bench	regex: Enable test on Windows	2014-08-18 13:44:29 +09:00
codegen
compile-fail	liblibc: don't use int/uint for intptr_t/uintptr_t	2014-08-20 21:02:24 -04:00
compile-fail-fulldeps	regex: Enable test on Windows	2014-08-18 13:44:29 +09:00
debuginfo	librustc: handle repr on structs, require it for ffi, unify with packed	2014-08-20 21:02:23 -04:00
pretty	librustc: Forbid external crates, imports, and/or items from being	2014-08-16 19:32:25 -07:00
run-fail	librustc: Forbid external crates, imports, and/or items from being	2014-08-16 19:32:25 -07:00
run-make	librustc: handle repr on structs, require it for ffi, unify with packed	2014-08-20 21:02:23 -04:00
run-pass	liblibc: don't use int/uint for intptr_t/uintptr_t	2014-08-20 21:02:24 -04:00
run-pass-fulldeps	Followup to PR #16477: a run-pass regression test for Issue #15750.	2014-08-14 11:55:47 +02:00