rust/src/librustc_codegen_ssa/back/linker.rs, branch 1.37.0 https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.37.0 2019-06-15T10:18:09+00:00 Auto merge of #59752 - Zoxc:dylib-fix, r=alexcrichton 2019-06-15T10:18:09+00:00 bors bors@rust-lang.org 2019-06-15T10:18:09+00:00 urn:sha1:dbebcee8d07b77eae3725988879001e6205c6e47 Limit dylib symbols This makes `windows-gnu` match the behavior of `windows-msvc`. It probably doesn't make sense to export these symbols on other platforms either. Unify all uses of 'gcx and 'tcx. 2019-06-14T15:58:23+00:00 Eduard-Mihai Burtescu edy.burt@gmail.com 2019-06-13T21:48:52+00:00 urn:sha1:f3f9d6dfd92dfaeb14df891ad27b2531809dd734 Add a limit_rdylib_exports option and disable it for Solaris 2019-06-12T21:07:13+00:00 John Kåre Alsaker john.kare.alsaker@gmail.com 2019-04-14T17:05:21+00:00 urn:sha1:52bd4f263b57faf987dc32d40642403e313e175a Limit dylib symbols 2019-06-12T21:07:12+00:00 John Kåre Alsaker john.kare.alsaker@gmail.com 2019-04-06T16:07:53+00:00 urn:sha1:185dcebbff7f3c18fb94be82f76bdfd620cfb096 rustc: replace `TyCtxt<'tcx, 'gcx, 'tcx>` with `TyCtxt<'gcx, 'tcx>`. 2019-06-12T10:38:27+00:00 Eduard-Mihai Burtescu edy.burt@gmail.com 2019-06-11T20:47:08+00:00 urn:sha1:17cdd356da598eb46515352277d3664f05c888ee rustc: Always handle exported symbols on the wasm target 2019-05-03T21:09:01+00:00 Alex Crichton alex@alexcrichton.com 2019-05-03T20:59:50+00:00 urn:sha1:884632cc796816fd9d3c8de60f2245c216f9a25a Currently when linking an artifact rustc will only conditionally call the `Linker::export_symbols` function, but this causes issues on some targets, like WebAssembly, where it means that executable outputs will not have the same symbols exported that cdylib outputs have. This commit sinks the conditional call to `export_symbols` inside the various implementations of the function that still need it, and otherwise the wasm linker is configured to always pass through symbol visibility lists. Rollup merge of #59320 - alexcrichton:wasm-clang, r=sanxiyn 2019-03-28T12:35:36+00:00 Mazdak Farrokhzad twingoow@gmail.com 2019-03-28T12:35:36+00:00 urn:sha1:9ca8f6aa796e97dec28f6cc2665d2fd3356d97ba rustc: Allow using `clang` for wasm32 targets This commit adds support code for using `clang` directly to link the wasm32-unknown-unknown target. Currently the target is only really configured to link with LLD directly, but this ensures that `clang` can be configured as well. While not immediately useful in the near term it's likely that more wasm32 targets will pop up over time with Clang's new native support for WebAssembly in the 8.0.0 release. Getting support into rustc early should make it easier to experiment with these targets and try out various changes here and there. Remove the block on natvis for lld-link. 2019-03-26T15:56:32+00:00 TheGoddessInari thegoddessinari@gmail.com 2019-03-26T15:46:41+00:00 urn:sha1:2a4281998b6cac4893dabea52d38518973bac41a rustc: Allow using `clang` for wasm32 targets 2019-03-20T21:42:53+00:00 Alex Crichton alex@alexcrichton.com 2019-03-19T20:06:37+00:00 urn:sha1:0e945411f2f54fdb3404b382844b9818ecc10b89 This commit adds support code for using `clang` directly to link the wasm32-unknown-unknown target. Currently the target is only really configured to link with LLD directly, but this ensures that `clang` can be configured as well. While not immediately useful in the near term it's likely that more wasm32 targets will pop up over time with Clang's new native support for WebAssembly in the 8.0.0 release. Getting support into rustc early should make it easier to experiment with these targets and try out various changes here and there. Use try blocks in rustc_codegen_ssa 2019-03-14T14:12:56+00:00 Taiki Endo te316e89@gmail.com 2019-03-14T14:12:56+00:00 urn:sha1:ab19e5870ea28584ecf3ff4885e29afbbcaf0854