<html>
<head>
<base href="https://llvm.org/bugs/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Do we need X86ISD::VSEXT and X86ISD::VZEXT?"
href="https://llvm.org/bugs/show_bug.cgi?id=31712">31712</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Do we need X86ISD::VSEXT and X86ISD::VZEXT?
</td>
</tr>
<tr>
<th>Product</th>
<td>libraries
</td>
</tr>
<tr>
<th>Version</th>
<td>trunk
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Windows NT
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>Backend: X86
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>llvm-dev@redking.me.uk
</td>
</tr>
<tr>
<th>CC</th>
<td>craig.topper@gmail.com, elena.demikhovsky@intel.com, llvm-bugs@lists.llvm.org, mkuper@google.com, spatel+llvm@rotateright.com
</td>
</tr>
<tr>
<th>Blocks</th>
<td>30624
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr></table>
<p>
<div>
<pre>Everything that X86ISD::VSEXT/X86ISD::VZEXT does can be performed with the ISD
SIGN/ZERO_EXTEND and SIGN/ZERO_EXTEND_VECTOR_IN_REG ops.
Using these directly would help us reuse existing generic combines and would
probably assist with (or at least avoid) various legalization/canonicalization
issues (such as what is going on with D28537).
AVX512 predicate mask extension may be tricky but it might make sense to keep
the X86ISD opcodes just for those cases, at least initially.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>