<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Issue</th>
<td>
<a href=https://github.com/llvm/llvm-project/issues/135874>135874</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>
[HLSL] clang-dxc emits dxv related warnings and errors when compiling to textual DXIL
</td>
</tr>
<tr>
<th>Labels</th>
<td>
HLSL
</td>
</tr>
<tr>
<th>Assignees</th>
<td>
</td>
</tr>
<tr>
<th>Reporter</th>
<td>
bogner
</td>
</tr>
</table>
<pre>
Running something like `clang-dxc.exe -T cs_6_2 x.hlsl` does one of two silly things, depending on whether `dxv` is on your path:
- warning: dxv not found; resulting DXIL will not be validated
- error: dxv command failed with exit code 1
The former makes sense when generating a binary (ie, with `-Fo out.dxil`), but it doesn't really make sense when we're generating text since the validator needs a binary anyway. The latter is even sillier, and results in all compiles to textual IR to fail if `dxv` is on your path.
We should only attempt to run `dxv` from the driver when emitting an object.
</pre>
<img width="1" height="1" alt="" src="http://email.email.llvm.org/o/eJx0k09v2zAMxT-NfCFi2PKfJAcf2hXBCvTUFdhuhWTRtlZZCiQ5sb_9QKX_LjslQcT3-H4kRQh6tIgda-5Z85CJJU7Od9KNFn0mndq658VabUcIbsY40Tej3xBYW_RG2HGn1j7HFWH3An14bV85rPlkgmFtAcphAGcR3ADx6iBoYzZIKoHxH6DwjFaRprNwnTBO6ElZrRcq11QMm1s8nEWcWHXHirsdXIWnjlh1B2q9gHURBrdYxap78BgWE0nx4c_jE1y1MemBRLgIo5WIqJIIeu_8h0Tv5llYBYPQBhVcdZwAVx2hdwqhZAUZv0wIg_MzepjFGwYIaANS2xZGtOhF8hUgtRV-A8YPGillkmNtsTs5cEvM1aqJDuNH-lcuEXRMqCzj-wgeBVEij-8WV2R87_G7VcQ1QtC2R4jTZ0DnwSKq8NWJsNtVbDlQAiNiRE9o8YI2TUSjp0YIwA1fAG1BGENcztpggOiS2SIMPD7TLyIFevj_sPIbtN8IYXKLUeCs2YDM53MkBb_Yb9WDd3MKoby-oL9FxlnHG1MLTv7FPuaZ6ip1rI4iw67c1_W-2fOiyaZO8qGsqn2lVK_KojygkPLAuTiUVYuywUx3vOBNUZcN53VbN_mxUIPsj7Jq27rp-YHVBc5Cm9yYy5w7P2Y6hAW7smoO-zozQqIJ6VA4__n064lxTifjO3q_k8sYWF0YHWL4Uog6mnRcqaB5gM-bSeFC2j6PhtbyY69DmkTaz3DjcBtDmvjXHGi_s8WbborxHOg2-Inx06jjtMi8dzPjJ-rj_WN39o4IMn5KsQLjp_dkl47_CwAA__9YC1ru">