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

    <tr>
        <th>Summary</th>
        <td>
            Short name for -fopenmp-targets for x86_64
        </td>
    </tr>

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

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

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

<pre>
    The arguments to `-fopenmp-targets` are triples.  Some platforms allow a shortened form with just the architecture (e.g .`-fopenmp-targets=nvptx64`). At the driver step, only the first part of the triple is checked.

In some cases (`amdgcn` and `nvptx64`), it doesn't matter what gets put in the rest of the triple (valid or not), the rest of the tool chain uses the correct value.

In this case of `x86_64`, the tool chain takes a different path depending on the rest of the triple.

If this is a supported feature, it needs tests.  Alternately, the input string needs better validation in the x86_64 case.
</pre>
<img width="1px" height="1px" alt="" src="http://email.email.llvm.org/o/eJx0k0Fvoz4QxT-NuYyCjAOEHjjk3yrS_9y9rwwewK2xkWdI2m-_MqQrNbt7SaSRee_3nj2ayI4esRXVf6J6yfTKU4jtrOO7wZv1Y9YF89n-mBB0HNcZPRNwAFHLwxAW9PNyYB1HZBK1BB0RONrFIeUAr2FGWJzmIcSZQDsXbqCBphAZPRpIc7hZnuBtJQbeXPrJMva8RgShGsxHyP_mdnzx14U_6lLUUqinHM67gIn2ihGIcRHqGYJ3n9t8sJEYFh0ZwrBNdlCwBP2E_TuaXMgXIc_77_8eKPH3mpASiailns3Y-y2oN6mDbwjJzjKYgOSFOjHMmhkj3CbNkJhhWRms38wj0iOIUM1VO2sgRPCB74p_HA7BQT9p62FNZGnWhxixZ7hqt-JjCp5SQk2YFEQtP5r65x35-VGR9TsSaDB2GDCiT4XxBAYX9Mb6EcK_6L-7DrurTVq0Lku6cAMD6nSt9548oiFgJE5v5ewYo9eM7vOLy_rUF3FMxvvpDrdGt5o02-C_6txDbTHzzLRH83R80hm2RX2q1OlUFTKb2hNiVVWnslBdVxQ1GlkcpTJVZUytyqbKbKukOkoli6Kpikrm-qRkqUxjOlkfy6EUpcRZW5c7d53zEMfMEq3Y1rKsmszpDh19rVJs06FDt44kSulsyvn7M7bssH1NmwBez5hWAR7f-Dbck2VrdO3EvJA4noW6CHUZLU9rl_dhFuqShO9_hyWGN-xZqMsGR0JdNr5fAQAA__84Eky4">