-
Notifications
You must be signed in to change notification settings - Fork 154
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
On Arm platform tests for group functions failed when targeting omp.accelerated #1431
Comments
Yes, it is expected to work on ARM, and was tested on A64fx and ThunderX2, but I don't know if anybody has ever tried it on Altra. @nilsfriess, I recall you recently reported to have found some bugs in the tests. Were the group tests by chance among the problematic test cases? |
Thanks for the info! I've also tested it on the Apple M1 Arm chip. Except for acpp, all dependencies are installed from official Debian or LLVM repos. cmake -DWITH_SSCP_COMPILER=OFF -DWITH_ACCELERATED_CPU=ON -DWITH_OPENCL_BACKEND=OFF -DCMAKE_INSTALL_PREFIX=$HOME/Projects/AdaptiveCpp/install -DWITH_CUDA_BACKEND=OFF -DWITH_ROCM_BACKEND=OFF -DWITH_LEVEL_ZERO_BACKEND=OFF -DDEFAULT_TARGETS='omp.accelerated' .. Identical failures to group functions happened. |
I only found some UB in the tests, but I don't think the group tests were among the problematic tests. But I'll check again |
Checked again, there is actually a problem in the group tests (an integer overflow, to be specific). Not sure if this can explain the error reported above. |
@ouankou Can you check whether it works as expected with |
Bug summary
Acpp can be built without issue on Oracle A1 VPS (4-core Ampere Altra chip). However, the built-in tests for group functions all failed.
I saw this issue related to Arm: #1044
It seems acpp has been tested on Arm. I'm wondering if I didn't set up acpp correctly.
To Reproduce
# build acpp and builtin tests ./sycl_tests --run_test=group_functions_tests
Expected behavior
All tests should pass.
Describe your setup
CPU: Ampere Altra (Arm Neoverse-N1, 4 cores)
RAM: 24 GB
OS: Debian 12
Software: Boost 1.74, Python 3.11
Build from source in GitHub repo develop branch
Clang/LLVM 17.0.6 from official LLVM apt repo.
GCC 12.2 from official Debian repo
acpp
. In particular, which backends and hardware you have compiled for:Optional additional diagnostic information
The following information can potentially help us:
HIPSYCL_DRYRUN=1
during compilation will causesyclcc
to print the commands it would execute instead of actually executing. This can help verify the sanity of your setup.syclcc --hipsycl-version
prints information about the AdaptiveCpp configuration that may be interesting for setup-related issues.For issues related to the runtime, setting the environment variable
ACPP_DEBUG_LEVEL=3
will cause it to print a lot of diagnostic information that might be helpful. Attach the output of your program withACPP_DEBUG_LEVEL=3
if you think it might be helpful for your issue.Execution output (fail.log) and DEBUG output(fail_output.log) are attached.
fail.log
fail_debug.log
Recent AdaptiveCpp versions include a tool called
acpp-info
, which will print information about available backends and devices. This may be interesting for issues related to e.g. device visibility.Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: