[Openmp-commits] [PATCH] D42427: Fix broken OpenMP runtime test cases for Windows

[Olga Malysheva via Phabricator via Openmp-commits]

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 ********************

Script:
-------

C:/src/llvm/build.release/./bin/clang.exe -fopenmp  -I C:/src/llvm/projects/openmp/runtime/test -I C:/src/llvm/build.release/projects/openmp/runtime/src -L C:/src/llvm/build.release/bin  C:\src\llvm\projects\openmp\runtime\test\ompt\misc\control_tool_no_ompt_support.c -o C:\src\llvm\build.release\projects\openmp\runtime\test\ompt\misc\Output\control_tool_no_ompt_support.c.tmp && C:\src\llvm\build.release\projects\openmp\runtime\test\ompt\misc\Output\control_tool_no_ompt_support.c.tmp

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 file>

To link with the libomp.dll in run-time set PATH to where libomp.dll is located.


https://reviews.llvm.org/D42427