https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.30.0 2018-08-31T13:22:52+00:00 2018-08-31T13:22:52+00:00 Michael Woerister michaelwoerister@posteo 2018-08-17T13:25:46+00:00 urn:sha1:2e587df6e2215b9dd053879d2ad42044781fc1c4 2018-08-28T20:32:11+00:00 Alex Crichton alex@alexcrichton.com 2018-08-23T18:03:22+00:00 urn:sha1:1fd45a13dee17701fc0aeaa847c1919d485d09fd 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 2018-08-20T06:46:32+00:00 Alex Crichton alex@alexcrichton.com 2018-08-20T06:44:25+00:00 urn:sha1:9d54bf8df2677dd5f985838c5686efaa24a73b6c In some profiling on OSX I saw the `write` syscall as quite high up on the profiling graph, which is definitely not good! It looks like we're setting the output stream of an object file as directly to a file descriptor which means that we run the risk of doing lots of little writes rather than a few large writes. This commit fixes this issue by adding a buffered stream on the output, causing the `write` syscall to disappear from the profiles on OSX. 2018-08-12T17:59:33+00:00 whitequark whitequark@whitequark.org 2018-08-12T17:59:18+00:00 urn:sha1:66fd1ebfae2fff815f27bf2be19469f40dd99c88 Fixes #35741. 2018-08-01T13:32:22+00:00 David Craven david@craven.ch 2018-07-24T10:03:28+00:00 urn:sha1:2d5f62fb48536d69aa7de0d7504df278271ccf25 2018-08-01T08:12:45+00:00 Pietro Albini pietro@pietroalbini.org 2018-08-01T08:12:45+00:00 urn:sha1:61b9a516d3c0495596b21fae10eab0f82c4c7f7f Fix -Wpessimizing-move warnings in rustllvm/PassWrapper These are producing warnings when building rustc (`warning: moving a local object in a return statement prevents copy elision [-Wpessimizing-move]`). 2018-07-30T17:10:25+00:00 Irina Popa irinagpopa@gmail.com 2018-07-10T15:00:02+00:00 urn:sha1:ebec156abfc25ce695227ed2c12c420244a433f8 2018-07-29T11:20:06+00:00 varkor github@varkor.com 2018-07-29T11:20:06+00:00 urn:sha1:9ccd7eef1eeda8d207f62dae0c32d35cad7fa826 2018-07-23T13:42:23+00:00 bors bors@rust-lang.org 2018-07-23T13:42:23+00:00 urn:sha1:5665a2d36778693ca19215540a518ccf04eb0b1a rustc: Work around an upstream wasm ThinLTO bug This commit implements a workaround for an [upstream LLVM bug][1] where custom sections were accidentally duplicated amongst codegen units when ThinLTO passes were performed. This is due to the fact that custom sections for wasm are stored as metadata nodes which are automatically imported into modules when ThinLTO happens. The fix here is to forcibly delete the metadata node from imported modules before LLVM has a chance to try to copy it over. [1]: https://bugs.llvm.org/show_bug.cgi?id=38184 2018-07-18T19:12:53+00:00 Alex Crichton alex@alexcrichton.com 2018-07-18T19:12:53+00:00 urn:sha1:e08fcbbd8d241ab68d72dc8b288ca55b8c1114fe This commit implements a workaround for an [upstream LLVM bug][1] where custom sections were accidentally duplicated amongst codegen units when ThinLTO passes were performed. This is due to the fact that custom sections for wasm are stored as metadata nodes which are automatically imported into modules when ThinLTO happens. The fix here is to forcibly delete the metadata node from imported modules before LLVM has a chance to try to copy it over. [1]: https://bugs.llvm.org/show_bug.cgi?id=38184