Uh oh!
There was an error while loading. Please reload this page.
Bump compiler-builtins to 0.1.15 - #60981
Conversation
alexcrichton
commented
May 20, 2019
r? @cuviper |
rust-highfive
commented
May 20, 2019
(rust_highfive has picked a reviewer for you, use r? to override) |
cuviper
commented
May 20, 2019
What is the impact of not having that |
alexcrichton
commented
May 20, 2019
The theoretical impact is that some binaries won't link if an intrinsic hasn't been ported from C to Rust (although that's pretty rare) or a binary may run a bit slower if an optimized assembly routine isn't included and instead a slower Rust routine is. Our distribution targets don't need it enabled afaik but we've never tried to build them without it afaik. This is probably going to regress something somewhere, but nothing major that I know of in the sense that it's probably some esoteric configuration in one way or another. |
cuviper
commented
May 20, 2019
OK, I just connected the dots on |
0e858e2 to
69c6326Comparealexcrichton
commented
May 20, 2019
A better comment definitely makes sense, but I don't really know of a great way to test this on CI that isn't overly invasive to our current config :( |
cuviper
commented
May 20, 2019
OK, thanks. I'll think more about CI myself, but I did test it locally too. @bors r+ |
bors
commented
May 20, 2019
📌 Commit 69c6326 has been approved by |
bors
commented
May 21, 2019
⌛ Testing commit 69c6326 with merge 4e4e986f9dc43c199ff1971ddc5d90ecf3c18d1c... |
bors
commented
May 21, 2019
💔 Test failed - checks-travis |
rust-highfive
commented
May 21, 2019
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
…ns, r=cuviper Bump compiler-builtins to 0.1.15 This commit bumps the `compiler-builtins` dependency to 0.1.15 which expects to have the source for `compiler-rt` provided externally if the `c` feature is enabled. This then plumbs through the necessary support in the build system to ensure that if the `llvm-project` directory is checked out and present that we enable the `c` feature of `compiler-builtins` and compile in all the C intrinsics.
Centril
commented
May 21, 2019
@bors retry Not fully sure if spurious or not... |
cuviper
commented
May 21, 2019
That path isn't valid -- it should be using something under @bors r- |
bors
commented
May 21, 2019
📌 Commit 3a132ea has been approved by |
…ns, r=cuviper Bump compiler-builtins to 0.1.15 This commit bumps the `compiler-builtins` dependency to 0.1.15 which expects to have the source for `compiler-rt` provided externally if the `c` feature is enabled. This then plumbs through the necessary support in the build system to ensure that if the `llvm-project` directory is checked out and present that we enable the `c` feature of `compiler-builtins` and compile in all the C intrinsics.
Centril
commented
May 22, 2019
Failed in #61032 (comment), @bors r- |
This commit bumps the `compiler-builtins` dependency to 0.1.15 which expects to have the source for `compiler-rt` provided externally if the `c` feature is enabled. This then plumbs through the necessary support in the build system to ensure that if the `llvm-project` directory is checked out and present that we enable the `c` feature of `compiler-builtins` and compile in all the C intrinsics.
3a132ea to
e59f0ccComparealexcrichton
commented
May 22, 2019
Looks like our old friend rust-lang/compiler-rt@d85fb9e never made its way into the llvm-project submodule (and for good reason!). I've now applied it and included it here. @bors: r=cuviper |
bors
commented
May 22, 2019
📌 Commit e59f0cc has been approved by |
…ns, r=cuviper Bump compiler-builtins to 0.1.15 This commit bumps the `compiler-builtins` dependency to 0.1.15 which expects to have the source for `compiler-rt` provided externally if the `c` feature is enabled. This then plumbs through the necessary support in the build system to ensure that if the `llvm-project` directory is checked out and present that we enable the `c` feature of `compiler-builtins` and compile in all the C intrinsics.
Rollup of 7 pull requests Successful merges: - #60981 (Bump compiler-builtins to 0.1.15) - #61014 (Make -Zemit-artifact-notifications also emit the artifact type) - #61043 (Disable LLVM/debug assertions in gnu-full-bootstrap) - #61046 (Fix ICE with inconsistent macro matchers) - #61055 (Solaris CI: Build with dilos2 stable) - #61057 (Revert "Add implementations of last in terms of next_back on a bunch of DoubleEndedIterators.") - #61073 (librustc_errors: Remove unused annotation style `OldSchoolNoteText`) Failed merges: r? @ghost
In rust-lang#60981 we switched to using src/llvm-project/compiler-rt inside compiler-builtins rather than a separate copy of it. In order to have the "c" feature turn on in builds from the source tarball, we need to include that path in its creation. fixesrust-lang#64239
…richton Include compiler-rt in the source tarball In rust-lang#60981 we switched to using src/llvm-project/compiler-rt inside compiler-builtins rather than a separate copy of it. In order to have the "c" feature turn on in builds from the source tarball, we need to include that path in its creation. fixesrust-lang#64239
In rust-lang#60981 we switched to using src/llvm-project/compiler-rt inside compiler-builtins rather than a separate copy of it. In order to have the "c" feature turn on in builds from the source tarball, we need to include that path in its creation. fixesrust-lang#64239
The assignment of `features` above was added in rust-lang#60981, but never used. Presumably the intent was to replace the string literal here with it. While I'm in the area, `compiler_builtins_c_feature` doesn't need to be a `String`.
…lexcrichton bootstrap: only use compiler-builtins-c if they exist The assignment of `features` above was added in rust-lang#60981, but never used. Presumably the intent was to replace the string literal here with it. While I'm in the area, `compiler_builtins_c_feature` doesn't need to be a `String`. I'm not entirely sure of a great way to locally test this -- `./x.py test` passed on my machine, but 🤷♂️. r? @alexcrichton
…lexcrichton bootstrap: only use compiler-builtins-c if they exist The assignment of `features` above was added in rust-lang#60981, but never used. Presumably the intent was to replace the string literal here with it. While I'm in the area, `compiler_builtins_c_feature` doesn't need to be a `String`. I'm not entirely sure of a great way to locally test this -- `./x.py test` passed on my machine, but 🤷♂️. r? @alexcrichton
This commit bumps the
compiler-builtinsdependency to 0.1.15 whichexpects to have the source for
compiler-rtprovided externally if thecfeature is enabled. This then plumbs through the necessary supportin the build system to ensure that if the
llvm-projectdirectory ischecked out and present that we enable the
cfeature ofcompiler-builtinsand compile in all the C intrinsics.