================
@@ -523,12 +545,13 @@ Error runSYCLLink(ArrayRef<std::string> Files, const
ArgList &Args) {
return createFileError(File, EC);
}
OffloadingImage TheImage{};
- TheImage.TheImageKind = IMG_Object;
+ TheImage.TheImageKind = IMG_None;
----------------
YuriPlyakhin wrote:
At this point yes, there are problems, if we use `IMG_SPIRV` and `IMG_Object`
due to incompatibility between data format used in upstream and Intel's
compiler forks. I tried using `IMG_SPIRV`, etc. and it opens can of worms.
I plan to do the clean-up and sync structures between upstream and Intel's
forks, but it is definitely a separate PR.
For this PR I used `IMG_None`, because in that case at least SYCL runtime has a
heuristic to understand what the Image Kind is, so we can at least verify that
overall compilation/linking scheme works.
https://github.com/llvm/llvm-project/pull/161287
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
