rust/src/rustllvm/PassWrapper.cpp, branch 1.32.0

Enable -mergefunc-use-aliases

2018-11-29T23:52:16+00:00

If the Rust LLVM fork is used, enable the -mergefunc-use-aliases flag, which will create aliases for merged functions, rather than inserting a call from one to the other. A number of codegen tests needed to be adjusted, because functions that previously fell below the thunk limit are now being merged. Merging is prevented either using -C no-prepopulate-passes, or by making the functions non-identical. I expect that this is going to break something, somewhere, because it isn't able to deal with aliases properly, but we won't find out until we try :) This fixes #52651.

Handle some renamed ThinLTO functions

2018-11-26T04:27:18+00:00

Auto merge of #55698 - nikic:remove-llvm-4-support, r=alexcrichton

2018-11-11T22:38:54+00:00

Remove support for building against LLVM 4 With emscripten removed in #55626, we no longer need to support building against LLVM 4.

Auto merge of #55626 - nikic:update-emscripten, r=alexcrichton

2018-11-10T01:16:02+00:00

Update emscripten This updates emscripten to 1.38.15, which is based on LLVM 6.0.1 and would allow us to drop code for handling LLVM 4. The main issue I ran into is that exporting statics through `EXPORTED_FUNCTIONS` no longer works. As far as I understand exporting non-functions doesn't really make sense under emscripten anyway, so I've modified the symbol export code to not even try. Closes #52323.

Remove support for building against LLVM 4

2018-11-05T14:04:26+00:00

With emscripten removed in #55626, we no longer need to support building against LLVM 4.

Update llvm-emscripten

2018-11-04T17:50:57+00:00

This updates emscripten to version 1.38.15, which is based on LLVM 6.0.1.

Remove checks for LLVM < 4.0

2018-11-01T20:09:02+00:00

While we still have to support LLVM 4.0 for Emscripten, we can drop checks for LLVM >= 4.0 and < 4.0.

add -Z emit-stack-sizes

2018-09-26T13:21:26+00:00

Provide a way of accessing the ThinLTO module import map in rustc.

2018-08-31T13:22:52+00:00

Fix warnings about the `native` target-cpu

2018-08-28T20:32:11+00:00

This fixes a regression from #53031 where specifying `-C target-cpu=native` is printing a lot of warnings from LLVM about `native` being an unknown CPU. It turns out that `native` is indeed an unknown CPU and we have to perform a mapping to an actual CPU name, but this mapping is only performed in one location rather than all locations we inform LLVM about the target CPU. This commit centralizes the mapping of `native` to LLVM's value of the native CPU, ensuring that all locations we inform LLVM about the `target-cpu` it's never `native`. Closes #53322