<table border="1" cellspacing="0" cellpadding="8">
    <tr>
        <th>Issue</th>
        <td>
            <a href=https://github.com/llvm/llvm-project/issues/62872>62872</a>
        </td>
    </tr>

    <tr>
        <th>Summary</th>
        <td>
            clang win32-msvc posing:  a minor mismatch logic while compiling pedantic
        </td>
    </tr>

    <tr>
      <th>Labels</th>
      <td>
            new issue
      </td>
    </tr>

    <tr>
      <th>Assignees</th>
      <td>
      </td>
    </tr>

    <tr>
      <th>Reporter</th>
      <td>
          mu578
      </td>
    </tr>
</table>

<pre>
    clang in msvc mode will complain about using language extension such as __int32 and __int64, that's alright...

However, many of their core APIs are expressly defined using those `extended` types... The entire `thing` is an extension to whatever anyways...

So, thus and then, is that can still be called a `language extension` wifffin (German version of within) such context, debatable.

Meanwhile, the important part: it won't complain about i64 or Ui64 suffix in a mix usage.

</pre>
<img width="1px" height="1px" alt="" src="http://email.email.llvm.org/o/eJxkkk-vqzYQxT-N2YwuIg7_smCR9iptF5UqtV1fDWaAqYyN7CEk374yuVXfu2-DETNwfudwMEaeHFGnqp9U9Z7hJrMP3bJVTZv1fnh2xqKbgB0s8W5g8QPBztaC8ctqkR1g7zeBLbKbIO1uOBHQQ8hF9g7iZmbACB8f7OSsAd3wuq9LpX8GmVGUbiKgDTzNkue5Kt5VcX1df_U73SmkzQXdE_wIMhMHMD4QXP_4LQKGJLcGitE-YaCRHQ2fPDL7SKDq4uAZaFB1AfJcKeZ5Dn_NBOSEw7EiM7spzTkCum8ciId9RkkcgO654zN-ofzTv6xs8bAnM7n0gONhDww6iJJC6wkMWksDYJL8Ma6kv_M4juxA6fYXCgs6uFM4SPwIOydOpS-vYI13Qg9JagP1KNhb-g7td0K3z2zpRUjAy-qDoBNYMYg6X4EFdu-UbuTrT-W6BB_g73TGbRz5kYqAsPADtojTf1LZ0J2Hy_mCGXWnui2btm6KNps7U2N1aZEabcjoU1tWQ9UMZW_qE51G6jPudKHPRaW1Lk6tbvNT1SKWTU1Vc7mMg1ZlQQuyza29L7kPU8YxbtTVum10ZrEnG4_yau1oh2OotE5dDl16563fpqjKwnKU-P9XhMXSZ7l3dmf9dvR79ak3KZXDpvMBFo4LipnB-okNHGEeQbFNFVtpQCdssi3YbhZZozpflb4pfZtY5q3PjV-UviXlz-NtDf4fMqL07eCNSt8OP_8GAAD__98WLbw">