rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2018-04-26	Rename rustc_back::target to rustc_target::spec.	Irina Popa	-34/+0

2018-04-26	rustc_back: move LinkerFlavor, PanicStrategy, and RelroLevel to target.	Irina Popa	-2/+1

2018-01-23	Set crt_static_default = false for musl/mips[el] targets	Marco A L Barbosa	-0/+1

2018-01-22	Do not assume dynamic linking for musl/mips[el] targets	Marco A L Barbosa	-11/+8
	All musl targets except mips[el] assume static linking by default. This can be confusing https://users.rust-lang.org/t/static-cross-compiled-binaries-arent-really-static/6084 When the musl/mips[el] targets was [added](https://github.com/rust-lang/rust/pull/31298), dynamic linking was chosen because of binary size concerns, and probably also because libunwind [didn't](https://users.rust-lang.org/t/static-cross-compiled-binaries-arent-really-static/6084/8) supported mips. Now that we have `crt-static` target-feature (the user can choose dynamic link for musl targets), and libunwind [6.0](https://github.com/llvm-mirror/libunwind/commits/release_60) add support to mips, we do not need to assume dynamic linking.
2017-09-30	rustc: Specify c_int width for each target	Daniel Klauer	-0/+1
	(all i32 for now, as in liblibc)
2017-07-05	rustc: Implement the #[global_allocator] attribute	Alex Crichton	-1/+1
	This PR is an implementation of [RFC 1974] which specifies a new method of defining a global allocator for a program. This obsoletes the old `#![allocator]` attribute and also removes support for it. [RFC 1974]: https://github.com/rust-lang/rfcs/pull/197 The new `#[global_allocator]` attribute solves many issues encountered with the `#![allocator]` attribute such as composition and restrictions on the crate graph itself. The compiler now has much more control over the ABI of the allocator and how it's implemented, allowing much more freedom in terms of how this feature is implemented. cc #27389
2017-04-07	-Z linker-flavor	Jorge Aparicio	-0/+2
	This patch adds a `-Z linker-flavor` flag to rustc which can be used to invoke the linker using a different interface. For example, by default rustc assumes that all the Linux targets will be linked using GCC. This makes it impossible to use LLD as a linker using just `-C linker=ld.lld` because that will invoke LLD with invalid command line arguments. (e.g. rustc will pass -Wl,--gc-sections to LLD but LLD doesn't understand that; --gc-sections would be the right argument) With this patch one can pass `-Z linker-flavor=ld` to rustc to invoke the linker using a LD-like interface. This way, `rustc -C linker=ld.lld -Z linker-flavor=ld` will invoke LLD with the right arguments. `-Z linker-flavor` accepts 4 different arguments: `em` (emcc), `ld`, `gcc`, `msvc` (link.exe). `em`, `gnu` and `msvc` cover all the existing linker interfaces. `ld` is a new flavor for interfacing GNU's ld and LLD. This patch also changes target specifications. `linker-flavor` is now a mandatory field that specifies the default linker flavor that the target will use. This change also makes the linker interface explicit; before, it used to be derived from other fields like linker-is-gnu, is-like-msvc, is-like-emscripten, etc. Another change to target specifications is that the fields `pre-link-args`, `post-link-args` and `late-link-args` now expect a map from flavor to linker arguments. ``` diff - "pre-link-args": ["-Wl,--as-needed", "-Wl,-z,-noexecstack"], + "pre-link-args": { + "gcc": ["-Wl,--as-needed", "-Wl,-z,-noexecstack"], + "ld": ["--as-needed", "-z,-noexecstack"], + }, ``` [breaking-change] for users of custom targets specifications
2016-10-27	Disable jemalloc on aarch64/powerpc	Alex Crichton	-0/+4
	Sounds like jemalloc is broken on systems which differ in page size than the host it was compiled on (unless an option was passed). This unfortunately reduces the portability of binaries created and can often make Rust segfault by default. For now let's patch over this by disabling jemalloc until we can figure out a better solution. Closes #36994 Closes #37320 cc jemalloc/jemalloc#467
2016-10-03	change max_atomic_width type from u64 to Option<u64>	Jorge Aparicio	-1/+1
	to better express the idea that omitting this field defaults this value to target_pointer_width
2016-07-27	librustc_back: convert fn target() to return Result	Doug Goldstein	-4/+4
	Change all the target generation functions to return a Result<Target, String> so that targets that are unable to be instantiated can be expressed as an Err instead of a panic!(). This should improve #33497 as well.
2016-05-09	Add #[cfg(target_has_atomic)] to get atomic support for the current target	Amanieu d'Antras	-0/+1

2016-04-19	Make data-layout mandatory in target specs.	Eduard Burtescu	-0/+1

2016-01-30	rustc: set MIPS cpu/features in the compiler	Jorge Aparicio	-2/+6
	cf #31303
2016-01-29	add support for mips(el)-unknown-linux-musl	Jorge Aparicio	-0/+24
	This target covers MIPS devices that run the trunk version of OpenWRT. The x86_64-unknown-linux-musl target always links statically to C libraries. For the mips(el)-unknown-linux-musl target, we opt for dynamic linking (like most of other targets do) to keep binary size down. As for the C compiler flags used in the build system, we use the same flags used for the mips(el)-unknown-linux-gnu target.