Explicitely set OMPT options for LLVM#3853
Conversation
> When defining a keyword argument before variable positional arguments, > one can end up in having multiple values passed for the aforementioned parameter > in case the method is called with keyword arguments.
|
Test report by @Flamefire Overview of tested easyconfigs (in order)
Build succeeded for 3 out of 3 (3 easyconfigs in total) |
|
@Crivella would you review this please? |
Co-authored-by: Davide Grassano <[email protected]>
This reverts commit 1982cae.
|
@boegelbot please test @ jsc-zen3 |
|
@Crivella: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 3136841522 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot Overview of tested easyconfigs (in order)
Build succeeded for 4 out of 4 (4 easyconfigs in total) |
|
Going in, thanks @Flamefire! |
As discussed here it makes sense to set
LIBOMP_OMPT_SUPPORTas that will cause a configure error instead of not building the tools interface with only a small configure messageAdditionally also set the related
LIBOMPTARGET_OMPT_SUPPORToptionNote that our definition of
build_openmp_toolsis not that ofOPENMP_ENABLE_OMPT_TOOLSbut rather matchesLIBOMP_OMPT_SUPPORT, see https://github.com/llvm/llvm-project/blob/adb2421202e4014b4986a9f1eb40833dc7ec25ad/openmp/README.rst#optional-featuresSo we enable more than just the interface, but I don't think we should change that.
Question: Should we also explicitely enable the optional OMPT features?
It currently defaults to ON, so we can ignore it.