I will try to look into OpenMP tests on Windows. I actually added the note (to
the discussion about failing tests) - how to make the particular test working.
But I need to build all this on Windows myself to verify and prepare the patch.
Currently I should admit it is much more difficult to build LLVM on Windows
than on Linux :(.
From: Jonas Hahnfeld [mailto:hah...@hahnjo.de]
Sent: Thursday, February 1, 2018 12:46 PM
To: Hans Wennborg <h...@chromium.org>
Cc: Joachim Protze <pro...@itc.rwth-aachen.de>; Malysheva, Olga
Subject: Re: [llvm-branch-commits] [cfe-branch] r323179 - [ReleaseNotes]
Mention OpenMP Tools Interface in runtime library
No, there isn't and I fully agree that this is far from ideal. However, we are
only running an x86 Linux cluster and that's where I try to get coverage for.
From my part, feel free to remove the part about Windows if you think it's
better for user experience. I've never used OpenMP on Windows and certainly
won't look into issues there.
Am 2018-02-01 10:38, schrieb Hans Wennborg:
> Is there a buildbot that tests it regularly on Windows, ideally built
> with Clang?
> I'm sorry that I seem grumpy about this, but there appears to be a
> problem here.
> On Thu, Feb 1, 2018 at 10:30 AM, Jonas Hahnfeld <hah...@hahnjo.de>
>> I think it actually works _if_ you get Clang to link to the right
>> runtime library... Adding Joachim and Olga who have been working on
>> this lately.
>> Am 2018-02-01 10:26, schrieb Hans Wennborg:
>> As far as I understand, this doesn't actually work on Windows.
>> we update the text?
>> On Tue, Jan 23, 2018 at 8:50 AM, Jonas Hahnfeld via
>> llvm-branch-commits <email@example.com> wrote:
>> Author: hahnfeld
>> Date: Mon Jan 22 23:50:11 2018
>> New Revision: 323179
>> URL: http://llvm.org/viewvc/llvm-project?rev=323179&view=rev  
>> [ReleaseNotes] Mention OpenMP Tools Interface in runtime library
>> The OpenMP runtime has no dedicated Release Notes, so add it to
>> Clang's section about OpenMP.
>> Differential Revision: https://reviews.llvm.org/D42352  
>> Modified: cfe/branches/release_60/docs/ReleaseNotes.rst
>> --- cfe/branches/release_60/docs/ReleaseNotes.rst (original)
>> +++ cfe/branches/release_60/docs/ReleaseNotes.rst Mon Jan 22
>> 23:50:11 2018
>> @@ -231,6 +231,13 @@ OpenMP Support in Clang
>> - Added support for `reduction`-based clauses on `task`-based
>> directives from upcoming OpenMP 5.0.
>> +- The LLVM OpenMP runtime `libomp` now supports the OpenMP Tools
>> Interface (OMPT)
>> + on x86, x86_64, AArch64, and PPC64 on Linux, Windows, and macOS.
>> If you observe
>> + a measurable performance impact on one of your applications
>> without a tool
>> + attached, please rebuild the runtime library with
>> `-DLIBOMP_OMPT_SUPPORT=OFF` and
>> + file a bug at `LLVM's Bugzilla <https://bugs.llvm.org/>`_ or send
>> a message to the
>> + `OpenMP development list
>> <http://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev 
>> Internal API Changes
Joint Stock Company Intel A/O
Registered legal address: Krylatsky Hills Business Park,
17 Krylatskaya Str., Bldg 4, Moscow 121614,
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
--- Begin Message ---
omalyshe added a comment.
> FAIL: libomp :: ompt/misc/control_tool_no_ompt_support.c (66 of 161)
- TEST 'libomp :: ompt/misc/control_tool_no_ompt_support.c' FAILED
C:/src/llvm/build.release/./bin/clang.exe -fopenmp -I
Does Clang on Windows accept -L option? I doubt.
To find new symbols like omp_control_tool at compile time the path to the
corresponding libomp.lib should be specified either by adding it to LIB
environment variable or by putting the libomp.lib with the full path to the
compiler command line:
$ clang -fopenmp -I <path to omp.h> <path to libomp.lib>\libomp.lib <source
To link with the libomp.dll in run-time set PATH to where libomp.dll is located.
--- End Message ---
llvm-branch-commits mailing list