Skip to content

[SYCL][L0] Fixed SYCL_PI_TRACE printing problem #2619

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

Merged
merged 4 commits into from
Oct 14, 2020

Conversation

glyons-intel
Copy link
Contributor

SYCL_PI_TRACE is used for internal debugging. It displays
the PI function that is being called and its arguments.

When piGetDeviceInfo() was called, the printing of the
pointer used for a variable sized string was incorrect.
Added a print() specialization.

The nullptr print() specialization was also updated because
specializations should be special.

Signed-off-by: Gail Lyons [email protected]

SYCL_PI_TRACE is used for internal debugging. It displays
the PI function that is being called and its arguments.

When piGetDeviceInfo() was called, the printing of the
pointer used for a variable sized string was incorrect.
Added a print() specialization.

The nullptr print() specialization was also updated because
specializations should be special.

Signed-off-by: Gail Lyons <[email protected]>
Signed-off-by: Gail Lyons <[email protected]>
smaslov-intel
smaslov-intel previously approved these changes Oct 13, 2020
@bader bader merged commit 2e9542a into intel:sycl Oct 14, 2020
@glyons-intel glyons-intel deleted the glyons/pitrace-fix branch January 28, 2021 21:33
kbenzie added a commit to kbenzie/intel-llvm that referenced this pull request Feb 17, 2025
…switch-redo

Move urMemImageGetInfo success test from a switch to individual test
Chenyang-L pushed a commit that referenced this pull request Feb 18, 2025
…h-redo

Move urMemImageGetInfo success test from a switch to individual test
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.

4 participants