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
Build error - comparison to zero in scalar_unary_red_omp.cc - both g++ and clang++ #84
Comments
Regarding the main issue, could you please try removing And just to confirm, are you on the latest commit from branch-21.10? Regarding your aside, it looks like the check for availability of |
Yep, I'm on branch-21.10 w/ the latest commit
Here's the full error on my OSX machine with Wfatal-errors disabled:
And thank you for submitting the __habs fix 👍 |
I think I have a fix on #86, waiting for it to pass CI. Please try it at your convenience and let me know if it fixes the issue for you. |
Yes that fixed it, and I'm able to run cg.py example on my Ubuntu machine. Thank you! 💯 |
Thanks for verifying, #86 has been merged, and the |
Summary:
There are 2 instances of what appears to be a comparison of a complex/bool/float (generic 'auto' variable) to zero in
unary/scalar_unary_red_omp.c
. g++ and clang++ both fail, saying there's no match for the!=
operator with the provided types.I've built legate.core (without cuda, see 'aside' at bottom of post) from source, have a pre-installed openblas, and get this error when building legate-numpy on both OSX and Ubuntu
Instances of zero comparison (unary/scalar_unary_red_omp.cc). Both trigger compiler errors
1:
2:
Command
On ubuntu (OSX command is similar):
Environment:
I'm encountering this error on both OSX and Ubuntu (and have tried a few different compilers):
OSX 10.15.7 Catalina
Compilers tried:
a. clang++ version 12.0.0.
b. clang++ Apple LLVM version 7.0.2 (clang-700.1.81)
c. g++-11 (Homebrew GCC 11.1.0) 11.1.0 (fails due to different errors).
Ubuntu 20.04.2 LTS (Focal Fossa)
Compilers tried:
a. g++ (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0.
Full error:
Changing the
0
to astd::complex<float>(0.0f,0.0f)
emits an error that the operand types are a bool and complex float.Perhaps I'm configuring something incorrectly, in which case any guidance is appreciated.
(Aside: My Ubuntu machine is GCP instance w/ a T4 GPU, running cuda 10.1. When kicking of a legate-core
with-cuda
build it fails as it can't recognize the "_habs" half precision function when building legionlegate/legate.core/legion/runtime/mathtypes/half.h(364): error: identifier "__habs" is undefined
. Looks like T4's Turing architecture isn't one of legate's supported platforms, but AFAIK Turing supports half precision)Thanks
The text was updated successfully, but these errors were encountered: