Skip to content
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

Bump XLA to 0.2.0 #486

Merged
merged 1 commit into from
Sep 24, 2021
Merged

Bump XLA to 0.2.0 #486

merged 1 commit into from
Sep 24, 2021

Conversation

jonatanklosko
Copy link
Member

Closes #217.

@josevalim josevalim merged commit 6fda0ce into elixir-nx:main Sep 24, 2021
@jonatanklosko jonatanklosko deleted the jk-bump-xla branch September 24, 2021 18:07
@zacky1972
Copy link
Contributor

zacky1972 commented Sep 24, 2021

I met the following error:

ERROR: /Users/zacky/.cache/xla_extension/tf-54dee6dd8d47b6e597f4d3f85b6fb43fd5f50f82/tensorflow/compiler/xla/extension/BUILD:101:20: invalid escape sequence: \/. You can enable unknown escape sequences by passing the flag --incompatible_restrict_string_escapes=false
ERROR: /Users/zacky/.cache/xla_extension/tf-54dee6dd8d47b6e597f4d3f85b6fb43fd5f50f82/tensorflow/compiler/xla/extension/BUILD:101:29: invalid escape sequence: \/. You can enable unknown escape sequences by passing the flag --incompatible_restrict_string_escapes=false
ERROR: /Users/zacky/.cache/xla_extension/tf-54dee6dd8d47b6e597f4d3f85b6fb43fd5f50f82/tensorflow/compiler/xla/extension/BUILD:102:20: invalid escape sequence: \/. You can enable unknown escape sequences by passing the flag --incompatible_restrict_string_escapes=false
ERROR: /Users/zacky/.cache/xla_extension/tf-54dee6dd8d47b6e597f4d3f85b6fb43fd5f50f82/tensorflow/compiler/xla/extension/BUILD:102:29: invalid escape sequence: \/. You can enable unknown escape sequences by passing the flag --incompatible_restrict_string_escapes=false
ERROR: /Users/zacky/.cache/xla_extension/tf-54dee6dd8d47b6e597f4d3f85b6fb43fd5f50f82/tensorflow/compiler/xla/extension/BUILD:104:19: invalid escape sequence: \/. You can enable unknown escape sequences by passing the flag --incompatible_restrict_string_escapes=false
ERROR: /Users/zacky/.cache/xla_extension/tf-54dee6dd8d47b6e597f4d3f85b6fb43fd5f50f82/tensorflow/compiler/xla/extension/BUILD:106:23: invalid escape sequence: \/. You can enable unknown escape sequences by passing the flag --incompatible_restrict_string_escapes=false
ERROR: Skipping '//tensorflow/compiler/xla/extension:xla_extension': no such target '//tensorflow/compiler/xla/extension:xla_extension': target 'xla_extension' not declared in package 'tensorflow/compiler/xla/extension' defined by /Users/zacky/.cache/xla_extension/tf-54dee6dd8d47b6e597f4d3f85b6fb43fd5f50f82/tensorflow/compiler/xla/extension/BUILD
WARNING: Target pattern parsing failed.
ERROR: no such target '//tensorflow/compiler/xla/extension:xla_extension': target 'xla_extension' not declared in package 'tensorflow/compiler/xla/extension' defined by /Users/zacky/.cache/xla_extension/tf-54dee6dd8d47b6e597f4d3f85b6fb43fd5f50f82/tensorflow/compiler/xla/extension/BUILD
INFO: Elapsed time: 0.092s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (1 packages loaded)
FAILED: Build did NOT complete successfully (1 packages loaded)
make: *** [/Users/zacky/github/nx_nif/deps/xla/cache/build/xla_extension-aarch64-darwin-cpu.tar.gz] Error 1

I can fix it temporally by the modification $HOME/.cache/xla_extension/tf-54dee6dd8d47b6e597f4d3f85b6fb43fd5f50f82/tensorflow/compiler/xla/extension/BUILD as follows:

diff ~/.cache/xla_extension/tf-54dee6dd8d47b6e597f4d3f85b6fb43fd5f50f82/tensorflow/compiler/xla/extension/BUILD ~/.cache/xla_extension/tf-54dee6dd8d47b6e597f4d3f85b6fb43fd5f50f82/tensorflow/compiler/xla/extension/BUILD.bak
101,102c101,102
<       d="$${d/llvm\\/include\\/llvm/llvm}"
<       d="$${d/llvm\\/include\\/llvm-c/llvm-c}"
---
>       d="$${d/llvm\/include\/llvm/llvm}"
>       d="$${d/llvm\/include\/llvm-c/llvm-c}"
104c104
<       d="$${d/src\\/google/google}"
---
>       d="$${d/src\/google/google}"
106c106
<       d="$${d/include\\/grpc/grpc}"
---
>       d="$${d/include\/grpc/grpc}"

Then I met the following error:

ERROR: /private/var/tmp/_bazel_zacky/28edfec9fbf3ed3b1fb5d31e37f4bf1d/external/local_config_cc/BUILD:48:19: in cc_toolchain_suite rule @local_config_cc//:toolchain: cc_toolchain_suite '@local_config_cc//:toolchain' does not contain a toolchain for cpu 'darwin_arm64'
ERROR: Analysis of target '//tensorflow/compiler/xla/extension:xla_extension' failed; build aborted: Analysis of target '@local_config_cc//:toolchain' failed
INFO: Elapsed time: 3.955s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (70 packages loaded, 355 targets configured)
FAILED: Build did NOT complete successfully (70 packages loaded, 355 targets configured)
make: *** [/Users/zacky/github/nx_nif/deps/xla/cache/build/xla_extension-aarch64-darwin-cpu.tar.gz] Error 1

I fix it temporally as follows:

% diff /private/var/tmp/_bazel_zacky/28edfec9fbf3ed3b1fb5d31e37f4bf1d/external/local_config_cc/BUILD /private/var/tmp/_bazel_zacky/28edfec9fbf3ed3b1fb5d31e37f4bf1d/external/local_config_cc/BUILD.bak 
55d54
<         "darwin_arm64": ":cc-compiler-darwin",

Then I met the following error:

ERROR: While resolving toolchains for target //tensorflow/tools/git:gen_git_source: No matching toolchains found for types @bazel_tools//tools/cpp:toolchain_type. Maybe --incompatible_use_cc_configure_from_rules_cc has been flipped and there is no default C++ toolchain added in the WORKSPACE file? See https://github.com/bazelbuild/bazel/issues/10134 for details and migration instructions.
ERROR: Analysis of target '//tensorflow/compiler/xla/extension:xla_extension' failed; build aborted: No matching toolchains found for types @bazel_tools//tools/cpp:toolchain_type. Maybe --incompatible_use_cc_configure_from_rules_cc has been flipped and there is no default C++ toolchain added in the WORKSPACE file? See https://github.com/bazelbuild/bazel/issues/10134 for details and migration instructions.

@zacky1972
Copy link
Contributor

Above mentioned errors seem to be fixed by updating EXLA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

XLA doesn't support Mac ARM
4 participants