<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 --- - inconsistent opcode enums between AXV-512 and AVX/AVX2"
   href="https://llvm.org/bugs/show_bug.cgi?id=31079">31079</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>inconsistent opcode enums between AXV-512 and AVX/AVX2
          </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>zvi.rackover@intel.com
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>llvm-bugs@lists.llvm.org
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr></table>
      <p>
        <div>
        <pre>I am creating this ticket in behalf of Gadi Haber who is waiting for his
Bugzilla account to be created.

There are cases of X86 AVX-512 opcode enums that are inconsistent with their
corresponding AVX opcode enums.
For example, the AVX-512 opcode: VBROADCASTSDZm  (without an â€˜r’ letter in its
suffix) has a corresponding AVX/AVX2 opcode VBROADCASTSDYrm which does include
the â€˜r’ letter in its suffix.
For these cases it is recommended to rename the AVX-512 enums to be consistent
with the AVX counterpart.

See the table below of all such cases:

Current AVX-512  Proposed enum renaming 
enum naming:     for consistency with  AVX/AVX2:

VBROADCASTSDZm    VBROADCASTSDZrm
VBROADCASTSDZr    VBROADCASTSDZrr
VBROADCASTSSZm    VBROADCASTSSZrm
VBROADCASTSSZr    VBROADCASTSSZrr
VPBROADCASTZr      VPBROADCASTZrr
VPBROADCASTZm      VPBROADCASTZrm
VPBROADCASTBrZr    VPBROADCASTBZrr
VPBROADCASTZm    VPBROADCASTZrm
VPBROADCASTZr      VPBROADCASTZrr
VPEXTRWZrr    VPEXTRWZri 
VPINSRWZrr    VPINSRWZrri
VPINSRWZrm    VPINSRWZrmi
VPSLLDQZrr    VPSLLDQZri
VPSRLDQZrr    VPSRLDQZri</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>