BukeBeyond wrote: > It's not actually clang's responsibility to not break your transformation. We > don't want to break it gratuitously, but if clang is generating correct code, > your transformation needs to be flexible enough to handle it. If there's > something easy we can do to help your transformation continue to work while > still compiling the source language properly, of course, we're absolutely > open to requests.
Understandably, Nvidia, AMD, Apple, all have self interests to sabotage genuine interoperability through Vulkan Compute. The short sightedness here is that, when you do that, you also slow down your own adaption of your own hardware. Software developers want to build once and have it work everywhere, despite your pursuits to cage them. Ultimately, this results in underutilization of your hardware. Who knows what other optimizations this commit has broken. We are fine to branch off of it as it is easy enough to disable. https://github.com/llvm/llvm-project/pull/115821 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
