https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.36.0 2019-04-26T15:58:14+00:00 2019-04-26T15:58:14+00:00 Josh Stone jistone@redhat.com 2019-04-26T15:58:14+00:00 urn:sha1:b4131e297e18fde119f6f461b3e622218166b009 2019-04-06T00:48:23+00:00 Josh Stone jistone@redhat.com 2019-04-06T00:48:23+00:00 urn:sha1:aafe2c6da93373b5f612c406037c5b75ba9deb46 I was trying to output LLVM IR directly to the console: $ rustc hello.rs --emit=llvm-ir -o /dev/stdout LLVM ERROR: IO failure on output stream: Bad file descriptor Now `LLVMRustPrintModule` returns an error, and we print: error: failed to write LLVM IR to /dev/stdout.hello.7rcbfp3g-cgu.0.rcgu.ll: Permission denied ... which is more informative. 2019-02-12T12:58:31+00:00 Alex Crichton alex@alexcrichton.com 2019-02-11T15:46:04+00:00 urn:sha1:e983b4f64ee6d919a60938b6e7371a66877f4a23 Currently the compiler will produce an error if both incremental compilation and full fat LTO is requested. With recent changes and the advent of incremental ThinLTO, however, all the hard work is already done for us and it's actually not too bad to remove this error! This commit updates the codegen backend to allow incremental full fat LTO. The semantics are that the input modules to LTO are all produce incrementally, but the final LTO step is always done unconditionally regardless of whether the inputs changed or not. The only real incremental win we could have here is if zero of the input modules changed, but that's so rare it's unlikely to be worthwhile to implement such a code path. cc #57968 cc rust-lang/cargo#6643 2019-01-25T23:39:54+00:00 Josh Stone jistone@redhat.com 2019-01-16T17:59:03+00:00 urn:sha1:df0466d0bb807a7266cc8ac9931cd43b3e84b62e The new git submodule src/llvm-project is a monorepo replacing src/llvm and src/tools/{clang,lld,lldb}. This also serves as a rebase for these projects to the new 8.x branch from trunk. The src/llvm-emscripten fork is unchanged for now. 2018-12-26T04:08:33+00:00 Mark Rousskov mark.simulacrum@gmail.com 2018-12-25T15:56:47+00:00 urn:sha1:2a663555ddf36f6b041445894a8c175cd1bc718c 2018-12-09T11:05:40+00:00 Nikita Popov nikita.ppv@gmail.com 2018-12-09T10:20:20+00:00 urn:sha1:706e67b0a0143d651eb03f2fa2c30645899e81ff 2018-11-29T23:52:16+00:00 Nikita Popov nikita.ppv@gmail.com 2018-11-29T22:05:23+00:00 urn:sha1:cbf748993f59682f60dfe620eafea24124f737fb 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. 2018-11-26T04:27:18+00:00 Alex Crichton alex@alexcrichton.com 2018-11-09T21:09:32+00:00 urn:sha1:ae5b350d7757a70e53219bbb5e32ae149ad063e0 2018-11-11T22:38:54+00:00 bors bors@rust-lang.org 2018-11-11T22:38:54+00:00 urn:sha1:775eab58835f9bc0f1f01ccbb79725dce0c73b51 Remove support for building against LLVM 4 With emscripten removed in #55626, we no longer need to support building against LLVM 4. 2018-11-10T01:16:02+00:00 bors bors@rust-lang.org 2018-11-10T01:16:02+00:00 urn:sha1:06118eac4c602a22d2004c98756a95f2c5ec95d5 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.