rust/src/librustc_back/target/mipsel_unknown_linux_gnu.rs, branch 1.26.2

librustc_back: enable fpxx on 32-bit hardfloat mips targets

2018-03-08T13:16:02+00:00

See this page for details about FPXX: https://dmz-portal.mips.com/wiki/MIPS_O32_ABI_-_FR0_and_FR1_Interlinking Using FPXX is the most compatible floating point mode available and allows the generated code to work in both FR0 and FR1 modes of the processor. Using MSA (MIPS SIMD) requires FR1, so to use any MSA code we need a compatible floating point mode. This commit also sets nooddspreg (disabling the use of odd numbered single precision float registers) as recommended when enabling FPXX.

librustc_back: bump ISA level of mipsel targets to mips32r2

2018-03-08T11:52:41+00:00

rustc: Specify c_int width for each target

2017-09-30T13:54:08+00:00

(all i32 for now, as in liblibc)

rustc: Implement the #[global_allocator] attribute

2017-07-05T21:37:01+00:00

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

-Z linker-flavor

2017-04-07T15:52:42+00:00

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

Disable jemalloc on aarch64/powerpc

2016-10-27T15:08:33+00:00

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

change max_atomic_width type from u64 to Option

2016-10-04T04:45:40+00:00

to better express the idea that omitting this field defaults this value to target_pointer_width

librustc_back: convert fn target() to return Result

2016-07-27T17:28:40+00:00

Change all the target generation functions to return a Result 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.

Add #[cfg(target_has_atomic)] to get atomic support for the current target

2016-05-09T12:31:47+00:00

Make data-layout mandatory in target specs.

2016-04-19T13:08:45+00:00