rust/src/librustc_back/target/aarch64_linux_android.rs, branch 1.22.1

rustc: Specify c_int width for each target

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

(all i32 for now, as in liblibc)

-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

rustc: Link to Android ABI requirements.

2016-12-16T19:27:12+00:00

Hopefully these references will be stable and provide guidance when requirements change in the future.

check target abi support

2016-10-24T13:59:53+00:00

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

Auto merge of #34743 - badboy:llvm-upgrade, r=eddyb

2016-08-01T11:47:48+00:00

LLVM upgrade As discussed in https://internals.rust-lang.org/t/need-help-with-emscripten-port/3154/46 I'm trying to update the used LLVM checkout in Rust. I basically took @shepmaster's code and applied it on top (though I did the commits manually, the [original commits have better descriptions](https://github.com/rust-lang/rust/compare/master...avr-rust:avr-support). With these changes I was able to build rustc. `make check` throws one last error on `run-pass/issue-28950.rs`. Output: https://gist.github.com/badboy/bcdd3bbde260860b6159aa49070a9052 I took the metadata changes as is and they seem to work, though it now uses the module in another step. I'm not sure if this is the best and correct way. Things to do: * [x] ~~Make `run-pass/issue-28950.rs` pass~~ unrelated * [x] Find out how the `PositionIndependentExecutable` setting is now used * [x] Is the `llvm::legacy` still the right way to do these things? cc @brson @alexcrichton

rustc: Fix data-layout for AArch64 targets

2016-07-29T08:29:44+00:00

Also relax the assertion whenever we have a custom LLVM root as LLVM may disagree about exact specifics.

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 all possible features (NEON, FP) to aarch64 android target.

2016-05-14T19:43:50+00:00

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

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