New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update stdsimd submodule #56178

Closed
wants to merge 1 commit into
base: master
from

Conversation

Projects
None yet
4 participants
@jethrogb
Contributor

jethrogb commented Nov 23, 2018

No description provided.

@rust-highfive

This comment has been minimized.

Collaborator

rust-highfive commented Nov 23, 2018

r? @aturon

(rust_highfive has picked a reviewer for you, use r? to override)

@rust-highfive

This comment has been minimized.

Collaborator

rust-highfive commented Nov 23, 2018

⚠️ Warning ⚠️

  • These commits modify submodules.
@rust-highfive

This comment has been minimized.

Collaborator

rust-highfive commented Nov 23, 2018

The job x86_64-gnu-llvm-5.0 of your PR failed on Travis (raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem.

Click to expand the log.
travis_time:end:0caccb04:start=1542953857766570812,finish=1542953858830289192,duration=1063718380
$ git checkout -qf FETCH_HEAD
travis_fold:end:git.checkout

Encrypted environment variables have been removed for security reasons.
See https://docs.travis-ci.com/user/pull-requests/#Pull-Requests-and-Security-Restrictions
$ export SCCACHE_BUCKET=rust-lang-ci-sccache2
$ export SCCACHE_REGION=us-west-1
Setting environment variables from .travis.yml
$ export IMAGE=x86_64-gnu-llvm-5.0
---
[00:53:16]     Checking compiler_builtins v0.0.0 (/checkout/src/rustc/compiler_builtins_shim)
[00:53:17]  Documenting alloc v0.0.0 (/checkout/src/liballoc)
[00:53:23]     Finished release [optimized] target(s) in 45.12s
[00:53:23]  Documenting core v0.0.0 (/checkout/src/libcore)
[00:53:28] error: cannot find macro `call!` in this scope
[00:53:28]   --> src/libcore/../stdsimd/coresimd/arm/armclang.rs:58:25
[00:53:28]    |
[00:53:28] 58 |     constify_imm8!(val, call);
[00:53:28]    |
[00:53:28]    |
[00:53:28]    = help: have you added the `#[macro_use]` on the module/import?
_64-unknown-linux-gnu/release
119368 ./obj/build/x86_64-unknown-linux-gnu/stage0-bootstrap-tools/x86_64-unknown-linux-gnu
119364 ./obj/build/x86_64-unknown-linux-gnu/stage0-bootstrap-tools/x86_64-unknown-linux-gnu/release
118444 ./obj/build/x86_64-unknown-linux-gnu/stage1-rustc/x86_64-unknown-linux-gnu/release/deps

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 @TimNN. (Feature Requests)

@jethrogb jethrogb force-pushed the jethrogb:jb/update-stdsimd branch 3 times, most recently from ca834c0 to fc14225 Nov 27, 2018

@rust-highfive

This comment has been minimized.

Collaborator

rust-highfive commented Nov 28, 2018

The job x86_64-gnu-llvm-5.0 of your PR failed on Travis (raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem.

Click to expand the log.
travis_time:end:09e4007b:start=1543385001619809772,finish=1543385056461914770,duration=54842104998
$ git checkout -qf FETCH_HEAD
travis_fold:end:git.checkout

Encrypted environment variables have been removed for security reasons.
See https://docs.travis-ci.com/user/pull-requests/#Pull-Requests-and-Security-Restrictions
$ export SCCACHE_BUCKET=rust-lang-ci-sccache2
$ export SCCACHE_REGION=us-west-1
Setting environment variables from .travis.yml
$ export IMAGE=x86_64-gnu-llvm-5.0
---
[00:46:04]     Checking compiler_builtins v0.0.0 (/checkout/src/rustc/compiler_builtins_shim)
[00:46:05]  Documenting alloc v0.0.0 (/checkout/src/liballoc)
[00:46:10]     Finished release [optimized] target(s) in 39.17s
[00:46:10]  Documenting core v0.0.0 (/checkout/src/libcore)
_64-unknown-linux-gnu/stage1-std/x86_64-unknown-linux-gnu/doc --markdown-css rust.css --markdown-no-toc --index-page /checkout/src/doc/index.md -L dependency=/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-std/x86_64-unknown-linux-gnu/release/deps -L dependency=/checkout/obj/build/x86_64-unknown-linux-gnu/stage1-std/release/deps` (exit code: 1)
[00:46:14] 
[00:46:14] 
[00:46:14] command did not execute successfully: "/checkout/obj/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "rustdoc" "--target" "x86_64-unknown-linux-gnu" "-j" "4" "--release" "--locked" "--color" "always" "--features" "panic-unwind backtrace" "--manifest-path" "/checkout/src/libstd/Cargo.toml" "-Z" "unstable-options" "-p" "core" "--" "--markdown-css" "rust.css" "--markdown-no-toc" "--index-page" "/checkout/src/doc/index.md"
[00:46:14] 
[00:46:14] 
[00:46:14] failed to run: /checkout/obj/build/bootstrap/debug/bootstrap doc
[00:46:14] Build completed unsuccessfully in 0:05:11
[00:46:14] Build completed unsuccessfully in 0:05:11
[00:46:14] Makefile:28: recipe for target 'all' failed
[00:46:14] make: *** [all] Error 1

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 @TimNN. (Feature Requests)

@jethrogb jethrogb force-pushed the jethrogb:jb/update-stdsimd branch 2 times, most recently from 868f4c3 to 256cac8 Nov 29, 2018

Jethro Beekman

@jethrogb jethrogb force-pushed the jethrogb:jb/update-stdsimd branch from 256cac8 to 7acb93f Nov 29, 2018

@jethrogb

This comment has been minimized.

Contributor

jethrogb commented Nov 29, 2018

This should now be ready for review. Alternatively, it will land as part of #56066.

@jethrogb

This comment has been minimized.

Contributor

jethrogb commented Dec 7, 2018

#56066 got merged with these changes.

@jethrogb jethrogb closed this Dec 7, 2018

@kennytm kennytm reopened this Dec 9, 2018

@kennytm kennytm closed this Dec 9, 2018

@rust-highfive

This comment has been minimized.

Collaborator

rust-highfive commented Dec 9, 2018

Your PR failed on Travis (raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem.

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 @TimNN. (Feature Requests)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment