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] Use CUDA_PATH as a candidate for path discovery #5194
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - does it make sense to add a test to be sure that the proper path is used when set?
I wanted to add a test at the time of writing this patch, but this is such an esoteric case that I failed to come up with anything. I don't know how we could re-create the condition in the testing environment. I'm tempted to say that this is also small/simple enough to maybe go without one? |
It's quite simple. Just set this environment variable for driver invocation, dump commands with |
I don't think that would work. Or at least not in the situation where this bug originally manifested. Clang would still fail to find the CUDA installation and fail the compilation, even though
|
It looks like the right option to use here is |
b1a741d
to
2f69e97
Compare
That's a great shout, added in: 7e86002 |
Co-authored-by: Alexey Bader <alexey.bader@intel.com>
@bader I thikn it is needed, as without it the compilation fails (because of the dummy
and as a result FileCheck just propagates the error:
Actually, I was just thinking, this test should stay in a separate file, as it requires |
Thanks for the clarification. Let's keep this test case in a separate file then. |
Co-authored-by: mdtoguchi <michael.d.toguchi@intel.com>
Fixes: #5028