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

    <tr>
        <th>Summary</th>
        <td>
            BUG: Update clang OpenMP conformance page to reflect actual implementation status
        </td>
    </tr>

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

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

    <tr>
      <th>Reporter</th>
      <td>
          h-vetinari
      </td>
    </tr>
</table>

<pre>
    Hi!

I help in the conda-forge ecosystem, which is like a cross-platform distribution of non-system libraries. Our compiler stack on osx is LLVM, and openmp is used in many other places too of course.

Being unable to follow the day-to-day development of literally hundreds of projects, I rely on release notes & status pages. For OpenMP there's https://clang.llvm.org/docs/OpenMPSupport.html, but this page seems un(der)maintained based on several observations:
* OpenMP 5.1 was recently made the default version in https://reviews.llvm.org/D129635, even though apparently ~60-70% of that standard aren't implemented according to the status page.
* OpenMP 5.2 is not mentioned even though features for that are being implemented ([example](https://github.com/llvm/llvm-project/commit/085845a2acbefd26d5c229338225dfd76e2c2df3)).
* There's very low commit [volume](https://github.com/llvm/llvm-project/commits/main/clang/docs/OpenMPSupport.rst) to that page, and (without pointing fingers, just using an example I came across today) commits like 085845a2acbefd26d5c229338225dfd76e2c2df3 don't update the status page despite implementing things.

It's important for users to know what clang supports, and arguably even more so for library authors & distributors, where the level of feature support across different openmp implementations is one of the key factors whether a feature can be used more broadly.

PS. Now that there's also flang in LLVM, the implementation status presumably also affects flang, resp. how flang presents its implementation status, see https://github.com/llvm/llvm-project/issues/62310.
</pre>
<img width="1px" height="1px" alt="" src="http://email.email.llvm.org/o/eJykVU2P2zgS_TX0pWBDoixbPvjQvY3ebSDZBMhm7yWyZDFNkQI_7Ogyv31Qkt1xBxlgBrmoG7Sq6r1Xj08Yozk5oqOoH0X9tMKceh-O_fpMyTgMZtV6PR3_Y4QsRfEkiofl-QI92RGMg9QTKO80rjsfTgSkfJxiokHIf8GlN6oHE8GaVwIEFXyM69Fi6nwYQJuYgmlzMt6B78B5t16KwZo2YDAUN_ApB1B-GI2lADGhegV-PX7nxh8-_P8jT0KnwY_khpFPcyTN4AZ0E_jUU4DRoqIIyXuepHwOkTb3lB7JuBNkh60lSB46b62_zPw0Tuvk1xon0HQm68eBXOI-1iQKaO0EfXY6kI58Ogb_jVSKDOwFAtmJEQeyhJHA-UQRhNwxmZQjjHhins8-wKeR3MfPPDSQkPsIfUpjFNWDkM9CPiuL7rSx9jxsfDgJ-ay9ikI-L2Vf8jj6kDZ9GiyPbnOC1JtlAESiIUJ2QjaagpCHAY1LaBxpaJEF8w4inZkP-DZSOCMvZp6-6CQfbgDrTQkXjBBIkUt2ggE1LVpRh9kmOFOIvFbjfuIQ6GzoEu9ZPJXysKtqxkxnYk_5fOoBxxHD0v6PXbHeF0LWLG_qMbF2TmPQwK8IuU9ghtESL4Y0oFI-aF5o8jOsO6k3v2Aj2TXOJ-B641mTeyQdYcqBInQ-LOMxELSzY-7HCtmI-pG-I5-J-knI5j35k0l9bjfKD0I-swLXP-urZXjHfhgM_1M0dbOtUaJqqdNyp2sl5aGqGilr3en9jqSSuquEPAh5uGP1vzf3nClMwC5emoKoH8_e5uH3sLHj2Dw3Q_6VD0NMQh6WDWCatb9dVSGbi2FxE4zeuMRCdsadKMyX5luOCXLkU3Rw1RNeQOFAgHOKQPIaJ-5_BbVkzN8VDbRfXJNHjYl-9ghoiqNJ9GO7s5d6407xXWq8pFloMzBjdGl2SI4UGCC8On-BC5OfhYK4KBNvMmA4ZWzttJht8IEg-rnFkn8TLIG8xMVbXPpFpQvveUZuOZX4alyNeht000qbrqMwZ9Y1I2-0livO7veOlstF8EoTdKh4Dg-Z8xPfeit00NKSsTPkNnjUdnqny-cvG_jvHJ-Y7uIMLfObtTDuLbx55ntEb7sIFPMwSzSXYtdxsC4tuDRQHDfQ-8u1KxeQSxHYEb_syVWRCP6x-U2MmdjlO1mVxWalj5U-VAdc0bHcNU3ZFI3cr_ojbXeNLLaq2mpVNlVbF3WJJFGVpSp1RytzlIWsin1RFvzcb7qmQlXR_tCWdSG3KLYFDWjsW0au5tnHXbWrqpXFlmycv9hSOrrA_KOQkj_g4TijbvMpim1hTUw_knaVTLJ0fPz6b1E9wNfF-Isxr0GovOMPMzpFyzVIHgJ1lhRbKWW0v9Z0lYM9_oagzOvPAAAA__-i5umK">