[Openmp-commits] [PATCH] D101509: An attempt to abandon omptarget out-of-tree builds.
Joachim Protze via Phabricator via Openmp-commits
openmp-commits at lists.llvm.org
Wed May 5 05:13:20 PDT 2021
protze.joachim added a comment.
In D101509#2733769 <https://reviews.llvm.org/D101509#2733769>, @jdoerfert wrote:
> In D101509#2725137 <https://reviews.llvm.org/D101509#2725137>, @protze.joachim wrote:
>
>> For me, the main use-case for stand-alone builds is runtime code development. In that case, I use a ("nightly") build of LLVM and use that to compile and test stand-alone runtime builds.
>> Switching branches regularly results in recompiling a lot of code. With stand-alone runtime builds, this is restricted to OpenMP runtime code.
>
> I don't really get why you would not rebase the runtime you are developing instead but as long as this doesn't block the patch it does not matter much.
The branch is not necessarily my branch. Even checking out the branch and temporary rebasing would touch enough files to trigger a rebuild of most of LLVM.
I just realized, that my other case for building OpenMP standalone is to get a debugging build. I usually only need the runtime libraries built with debug info. I could probably change the build type in the runtime build directory, but I prefer to build and install both release and debug runtime.
For debugging, I then only need to load my omp-debug module to pick the debug runtime during execution.
================
Comment at: openmp/README.rst:249-250
+
+- As a project of a regular LLVM build via **LLVM_ENABLE_PROJECTS** or
+ **LLVM_EXTERNAL_PROJECTS**, or
+- as a standalone project build that uses a pre-installed LLVM package.
----------------
or LLVM_ENABLE_RUNTIMES
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D101509/new/
https://reviews.llvm.org/D101509
More information about the Openmp-commits
mailing list