-
Notifications
You must be signed in to change notification settings - Fork 156
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
test code fails on first run #1455
Labels
bug
Something isn't working
Comments
(This was discovered together with me at the SYCL tutorial at ISC and is most likely related to adaptivity level=1 optimizations, perhaps kernel configuration object lifetime) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug summary
When I run this code from the codeplay demo, it fails on first run. The second time it runs fine.
To Reproduce
Steps to reproduce the behavior.
If possible, provide a minimal reproducer. The shorter the reproducing code snippet is, the easier will it be for us to debug and understand the issue.
clone and compile:
run:
Error I get
The second time it runs fine. Also if you use the flag
ACPP_ADAPTIVITY_LEVEL=0 ./a.out
it worksExpected behavior
A clear and concise description of what you expected to happen.
this is the output I get the second time (successful)
Describe your setup
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.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.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: