As support expands to more runtimes, we'll need to
distinguish between more than just HSA and unknown.
This also lets us stop using unknown everywhere.
Details
Diff Detail
Event Timeline
lib/Support/Triple.cpp | ||
---|---|---|
451 | I'm not sure about this one. It only really makes sense to use this with the amdgcn target. It seems like maybe this should be something more generic (mesa?). |
lib/Support/Triple.cpp | ||
---|---|---|
451 | Neither am I. Mesa should definitely be the vendor though, not the OS. Michel said on IRC that a mesa vulkan driver will probably end up using a different ABI, so we will probably need to distinguish those. |
Well you don't need a separate triple to handle an abi difference.
TargetOptions can take an abi name.
lib/Support/Triple.cpp | ||
---|---|---|
451 | AFAIK, there won't be any Mesa Vulkan driver. The Vulkan driver will be a completely separate project. |
Use mesa3d for the OS. The clover vs. graphics abi difference will be handled not as an OS
We've been treating the driver as the operating system. I have no idea what the OS would mean if mesa is an environment, The host OS is irrelevant. I'm still iffy about whether clover qualifies as a separate OS from the graphics driver, since it doesn't really share any of the same interface to kernels despite being another mesa project.
I'm not sure about this one. It only really makes sense to use this with the amdgcn target. It seems like maybe this should be something more generic (mesa?).