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

Fixing LIBOMPTARGET_INFO message, for Copying data from device to host #85444

Merged
merged 2 commits into from
Mar 15, 2024

Conversation

fel-cab
Copy link
Contributor

@fel-cab fel-cab commented Mar 15, 2024

When running OpenMP offloading application with LIBOMPTARGET_INFO=-1, the addresses of the Copying data from device to host, the address are swap.
As an example, Currently the address would be

omptarget device 0 info: Mapping exists with HstPtrBegin=0x00007ffddaf0fb90, TgtPtrBegin=0x00007fb385404000, Size=8000, DynRefCount=0 (decremented, delayed deletion), HoldRefCount=0
omptarget device 0 info: Copying data from device to host, TgtPtr=0x00007ffddaf0fb90, HstPtr=0x00007fb385404000, Size=8000, Name=d

And it should be

omptarget device 0 info: Copying data from device to host, TgtPtr=0x00007fb385404000, HstPtr=0x00007ffddaf0fb90, Size=8000, Name=d

…the printCopyInfoImpl when the copy was from the device to the host
@fel-cab fel-cab added the openmp:libomptarget OpenMP offload runtime label Mar 15, 2024
@fel-cab fel-cab requested a review from jdoerfert March 15, 2024 18:31
@fel-cab fel-cab self-assigned this Mar 15, 2024
Copy link

github-actions bot commented Mar 15, 2024

✅ With the latest revision this PR passed the C/C++ code formatter.

Copy link
Member

@jdoerfert jdoerfert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LG

@fel-cab fel-cab merged commit 0e21672 into llvm:main Mar 15, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
openmp:libomptarget OpenMP offload runtime
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants