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

[SYCL][CUDA] LIT SPIR-V test unsupported #1847

Conversation

bjoernknafla
Copy link
Contributor

Mark a LIT test that checks for SPIR-V specific trace output as
unsupported by CUDA as the CUDA plugin does not support SPIR-V.

Signed-off-by: Bjoern Knafla bjoern@codeplay.com

Mark a LIT test that checks for SPIR-V specific trace output as
unsupported by CUDA as the CUDA plugin does not support SPIR-V.

Signed-off-by: Bjoern Knafla <bjoern@codeplay.com>
@bjoernknafla bjoernknafla requested a review from a team as a code owner June 9, 2020 16:10
@bjoernknafla bjoernknafla requested a review from againull June 9, 2020 16:10
Copy link
Contributor

@againull againull left a comment

Choose a reason for hiding this comment

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

Does it make sense to save this scheduler test for CUDA by replacing this check by the check below?
// CHECK:---> pi{{[a-zA-Z_]*}}ProgramCreate{{[a-zA-Z_]*}}

@bjoernknafla
Copy link
Contributor Author

@againull That is a great idea! I will look into that.

@bader
Copy link
Contributor

bader commented Jun 9, 2020

@againull, what PI function we use to create a program in AOT mode with level0?

@againull
Copy link
Contributor

@againull, what PI function we use to create a program in AOT mode with level0?

piclProgramCreateWithBinary if i am not mistaken.

@bader
Copy link
Contributor

bader commented Jun 10, 2020

@againull, what PI function we use to create a program in AOT mode with level0?

piclProgramCreateWithBinary if i am not mistaken.

So, all backends including CUDA and level0 implement picl* function, which seems to be OpenCL specific.
Shoudn't we extend piCreateProgram with "Binary" format support in addition to SPIR-V?
Or remove the cl from the pi function name?

@smaslov-intel
Copy link
Contributor

Or remove the cl from the pi function name?

+1

Level-Zero supports piclProgramCreateWithBinary is is no longer OpenCL only (unlike piclProgramCreateWithSource)

@bjoernknafla
Copy link
Contributor Author

bjoernknafla commented Jun 10, 2020

I am not sure if I have testing of Level0 locally set up - if I change the PI function naming will the buildbots find if I missed something in Level0?

There are also tests with symbol dumps in them - not sure yet how they are created (seems that only the test file itself needs to be edited). As I have more pressing issues on my stack and the renaming might take more investigation than expected this PR might have to wait a bit.

@bader
Copy link
Contributor

bader commented Jun 10, 2020

I'm fine with doing renaming in a separate PR.

@bjoernknafla
Copy link
Contributor Author

I will close this PR then.

@bader
Copy link
Contributor

bader commented Jun 10, 2020

I will close this PR then.

I thought you are going to enable this test for CUDA following the suggestion from @againull

Does it make sense to save this scheduler test for CUDA by replacing this check by the check below?
// CHECK:---> pi{{[a-zA-Z_]*}}ProgramCreate{{[a-zA-Z_]*}}

@bjoernknafla
Copy link
Contributor Author

I will close this and then open a PR with the piclProgramCreateWithBinary to piProgramCreateWithBinary rename that should also enable this test for CUDA.

@bjoernknafla
Copy link
Contributor Author

Closing in favor for #1865

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