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

    <tr>
        <th>Summary</th>
        <td>
            clang msvc target gnu driver is missing a lot of options
        </td>
    </tr>

    <tr>
      <th>Labels</th>
      <td>
            clang
      </td>
    </tr>

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

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

<pre>
    The clang gnu driver lacks many of options specific to clang-cl, which makes cross-compiling `--target=*-pc-windows-msvc` an extreme pain.

1. clang does not support `-winsysroot`, which is fine for native compilation, clang can still find the Windows SDK, but it won't work when cross compilation, so users has to hack to provide `LIB` `INCLUDE` to clang. The UsersManual also mentions `WindowsSdkDir` environment variable, but that is not implemented.
2. clang does not support `-mguard=cf` and `-mguard=ehcont`, so users need to pass `-Xclang -cfguard -Xclang -ehcontguard` to cc manually, and then pass `-Wl,-guard:ehcont,longjump` to lld-link manually.
3. clang still use MSVC-style linker (lld-link) when using MSVC target, and silently ignoring `--ld-path` makes it impossible to transparently replace incompatible flags via a wrapper, which makes the clang gnu driver pointless: still incompatible with build systems that unspported MSVC.

My use case is cross compilation, since MinGW can't keep up with modern Windows these days, and even has a long history of antimalware false positives, and is not supported by giants like Google, Microsoft, NVIDIA, etc., I've tried to migrate to Windows SDK, but clang-cl is still not able to build much of what MinGW can build. Although there are vcpkg ports or similar package managers, I prefer to build everything from git master, so any patches and third-party ports are impractical for such use cases.

Ideally, I'd like some interoperability between clang and clang-cl, as well as ld.lld and lld-link, or at least some common options between them.
</pre>
<img width="1px" height="1px" alt="" src="http://email.email.llvm.org/o/eJx8VcFy2zgM_Rr5gpFHlhMnPviQxpuOZ5teum33CpOwhJoiNQRl13-_A1F2mk5nL2GiAODDw3sginDjiTbF_YfifjvDIbUhbp68xXhmP_yc7YO9bP5pCYxD30DjB7CRTxTBoTkKdOgvEA4Q-sTBC0hPhg9sIIWcUhpX1M9wbtm00OGRBEwMIqUJXc-OfQPFqirLhLGhVCy3Rf1U9qY8s7fhLGUnJ1OsKkAP9DNF6gh6ZD8vqm1RPeWfi_kEzwYS8CGBDH0fYhpLn9nLRWIIqVhVb1hY4MCe4BAieEx8IsiQUDvRuFzToAdJ7JyGW0gtwfeMDb5s_9a4_ZCAE5w160HPeIRzSz43-ntVCTAIRYEWRVlq0Rz17GM4sSWF_Gn3QVsuVtXu8_Onr9u_9K8roXPQcXzVEq_oB3SATgJ05PMEilU14ftij1uOmkv-xDF4jYETRsa9oyvy1GJSMpQ27npHGkV2Irj-X2q7ZsBoi-XWHPKM7PvP1Jrgr7TfGvdEduwYZYRb_puvKM1hTITbh5yfq00UGJXcgM5dtCbmifi3Wt9VbuUE4GkCUD-74JsfQ9dPZZyzpWN_vBWb2l1e280TH4Tg9cu351LSxRFoBkUo6sdrflGv86gHUSVrLExKntAJO_LJXYAbH-JN7s6WPaZW4WRT8Mh-EOG9I4WYInrpMebsSL1DQ8Be5YRpjDo4bAROjIBwjtj3FH_3WvqTdfvAPjkSKZZPU6fv6p45tbAf2FmQiyTqJKtk8DLOnuzY6TsPvl5GtgwKqZr-LH32huCV_cfvaqvRLUeiHoY-39kFS9Hf_JVaEgKLF7mySSfyo3EQdKLQsqQQxw2EPnGH7oyR4IBOCPogrL6-ZfM7BZOF_QUaRp8EHB8JPobQZGO8sjYQDuMYP3_bbXdP-hslM9dzV9QPJ4IUOSu54yZiGsf2h91w3YN6f2ZbUeA058xzN5hWuzgrzzeG8j_n8ORSG4amVUYigbZ4Mv2xAe1DIEQQ7thhhB7NERtSXWNDcWx9B32kA8W32-hE8ZJaVeMhhg4aTtChpKwfCaBbvcdkWpLJYxxVsTFdpjsVA3d9RJPYoBvXqGgTVxXIO3nsLF09q-TZTLiETiWdKIaeIu7ZcbrAntKZdH2OutXrf31JUOBMzunp7Nw5O0a8GfJZ6cAEjlBSvsGErgv-9kZd66eWuvnMbpZ2vVzjjDaLh8V9Vd2v6nrWbuwjLZfWVIaqh8rUZr98xOrO0mL9aNaPy8OMN3VV31X31WpxVz9Ui_l69fDwSGZ_Zwyt6wUVdxV1yG7u3Kmbh9jMWGSgzXpRL1Yzh3tyMr68dT02WNS1PsJxo_HlfmikuKscS5K3ComTo01mRp_Gadv86m4W6FjGfaQuSb88z7Mhuk2bUq_OL-qXon5pOLXDfm5CV9Qves10lH0MP8ikon4ZUUtRv4zA_wsAAP__P93SWQ">