Robin Kruppe 30daedf603 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-17 21:12:26 +01:00
..
archive_ro.rs	run rustfmt on librustc_llvm folder	2016-05-29 14:57:34 +05:30
build.rs	Rebuild rustc_llvm when the rustllvm source files change	2016-11-16 23:34:15 +01:00
Cargo.toml	Use llvm::Attribute API instead of "raw value" APIs, which will be removed in LLVM 4.0.	2016-11-17 21:12:26 +01:00
diagnostic.rs	run rustfmt on librustc_llvm folder	2016-10-22 18:37:35 +05:30
ffi.rs	Use llvm::Attribute API instead of "raw value" APIs, which will be removed in LLVM 4.0.	2016-11-17 21:12:26 +01:00
lib.rs	Use llvm::Attribute API instead of "raw value" APIs, which will be removed in LLVM 4.0.	2016-11-17 21:12:26 +01:00