Revert "[OpenMP][OMPD] GDB plugin code to leverage libompd to provide debugging"This reverts commit 51d3f421f48f7c888c37a13be049a4ca8b61436e.
Revert "Fixing build bot failure due to python-pip unavailability."This reverts commit 9dc0d6aaa1e27b97e5d163f2590cf24b769a0c36.
Fixing build bot failure due to python-pip unavailability.commit: 51d3f421f48f7c888c37a13be049a4ca8b61436efailed due to missing python-pip om machine.Now the ompd gdb-plugin code will be skipped
Fixing build bot failure due to python-pip unavailability.commit: 51d3f421f48f7c888c37a13be049a4ca8b61436efailed due to missing python-pip om machine.Now the ompd gdb-plugin code will be skipped with a warningif pip is not available in the machine.
show more ...
[OpenMP][OMPD] GDB plugin code to leverage libompd to provide debuggingsupport for OpenMP programs.This is 5th of 6 patches started from https://reviews.llvm.org/D100181This plugin code, when loa
[OpenMP][OMPD] GDB plugin code to leverage libompd to provide debuggingsupport for OpenMP programs.This is 5th of 6 patches started from https://reviews.llvm.org/D100181This plugin code, when loaded in gdb, adds a few commands likeompd icv, ompd bt, ompd parallel.These commands create an interface for GDB to read the OpenMPruntime through libompd.Reviewed By: @dreachemDifferential Revision: https://reviews.llvm.org/D100185
[Clang][OpenMP] libompd: get libomp hwloc includedir by target_link_librariesWhen hwloc is used and is installed outside of the default paths, the omp CMake targetneeds to provide the needed inclu
[Clang][OpenMP] libompd: get libomp hwloc includedir by target_link_librariesWhen hwloc is used and is installed outside of the default paths, the omp CMake targetneeds to provide the needed include path thru the CMake target by adding it withtarget_include_directories to it, so libompd gets it as well when it defines it's cmaketarget using target_link_libraries.As suggested in D122667Reviewed By: ye-luoDifferential Revision: https://reviews.llvm.org/D123888
[openmp][cmake] Use `GNUInstallDirs` to support custom installation dirsI am breaking apart D99484 so the cause of build failures is easier tounderstand.Differential Revision: https://reviews.ll
[openmp][cmake] Use `GNUInstallDirs` to support custom installation dirsI am breaking apart D99484 so the cause of build failures is easier tounderstand.Differential Revision: https://reviews.llvm.org/D117945
Revert "[cmake] Use `GNUInstallDirs` to support custom installation dirs."https://lab.llvm.org/buildbot/#/builders/46/builds/21146 Still havethis odd error, not sure how to reproduce, so I will ju
Revert "[cmake] Use `GNUInstallDirs` to support custom installation dirs."https://lab.llvm.org/buildbot/#/builders/46/builds/21146 Still havethis odd error, not sure how to reproduce, so I will just try breakingup my patch.This reverts commit 4a678f8072004eff9214c1a4e1836a14abb69535.
[cmake] Use `GNUInstallDirs` to support custom installation dirs.This is the original patch in my GNUInstallDirs series, now last to merge as the final piece!It arose as a new draft of D28234. I
[cmake] Use `GNUInstallDirs` to support custom installation dirs.This is the original patch in my GNUInstallDirs series, now last to merge as the final piece!It arose as a new draft of D28234. I initially did the unorthodox thing of pushing to that when I wasn't the original author, but since I ended up - Using `GNUInstallDirs`, rather than mimicking it, as the original author was hesitant to do but others requested. - Converting all the packages, not just LLVM, effecting many more projects than LLVM itself.I figured it was time to make a new revision.I have used this patch series (and many back-ports) as the basis of https://github.com/NixOS/nixpkgs/pull/111487 for my distro (NixOS), which was merged last spring (2021). It looked like people were generally on board in D28234, but I make note of this here in case extra motivation is useful.---As pointed out in the original issue, a central tension is that LLVM already has some partial support for these sorts of things. Variables like `COMPILER_RT_INSTALL_PATH` have already been dealt with. Variables like `LLVM_LIBDIR_SUFFIX` however, will require further work, so that we may use `CMAKE_INSTALL_LIBDIR`.These remaining items will be addressed in further patches. What is here is now rote and so we should get it out of the way before dealing more intricately with the remainder.Reviewed By: #libunwind, #libc, #libc_abi, compnerdDifferential Revision: https://reviews.llvm.org/D99484
Revert "[cmake] Use `GNUInstallDirs` to support custom installation dirs."Sorry for the disruption, I will try again later.This reverts commit efeb50197091b2ade24c00b9d55814bc433a7fd1.
[OpenMP][OMPD] Implementation of OMPD debugging library - libompd.This is a continuation of the review: https://reviews.llvm.org/D100183It contains routines that retrieve OpenMP ICV values for OMP
[OpenMP][OMPD] Implementation of OMPD debugging library - libompd.This is a continuation of the review: https://reviews.llvm.org/D100183It contains routines that retrieve OpenMP ICV values for OMPD.Reviewed By: @hbaeDifferential Revision: https://reviews.llvm.org/D100184
[OpenMP][OMPD] Implementation of OMPD debugging library - libompd.This is a continuation of the review: https://reviews.llvm.org/D100182This patch implements the OMPD API as specified in the stand
[OpenMP][OMPD] Implementation of OMPD debugging library - libompd.This is a continuation of the review: https://reviews.llvm.org/D100182This patch implements the OMPD API as specified in the standard doc.Reviewed By: @hbaeDifferential Revision: https://reviews.llvm.org/D100183
[OpenMP] [OMPD] OPENMP_INSTALL_LIBDIR is set for the install dirOPENMP_INSTALL_LIBDIR is set to the installation path of shared and staticlibompd.This should avoid the mixing of 32 and 64 bit on s
[OpenMP] [OMPD] OPENMP_INSTALL_LIBDIR is set for the install dirOPENMP_INSTALL_LIBDIR is set to the installation path of shared and staticlibompd.This should avoid the mixing of 32 and 64 bit on same path inmulti-lib set-up.Reviewed By: @mceierDifferential Revision: https://reviews.llvm.org/D109352
[OpenMP][OMPD] Implementation of OMPD debugging library - libompd.This is a continuation of the review: https://reviews.llvm.org/D100181Creates a new directory "libompd" under openmp."TargetValu
[OpenMP][OMPD] Implementation of OMPD debugging library - libompd.This is a continuation of the review: https://reviews.llvm.org/D100181Creates a new directory "libompd" under openmp."TargetValue" provides operational access to the OpenMP runtime memory for OMPD APIs.With TargetValue, using "pointer" a user can do multiple operationsfrom casting, dereferencing to accessing an element for structure.The member functions are designed to concatenate the operations thatare needed to access values from structures.e.g., _a[6]->_b._c would read like :TValue(ctx, "_a").cast("A",2) .getArrayElement(6).access("_b").cast("B").access("_c")For example:If you have a pointer "ThreadHandle" of a running program then you canaccess/retrieve "threadID" from the memory using TargetValue as below. TValue(context, thread_handle->th) /*__kmp_threads[t]->th*/ .cast("kmp_base_info_t") .access("th_info") /*__kmp_threads[t]->th.th_info*/ .cast("kmp_desc_t") .access("ds") /*__kmp_threads[t]->th.th_info.ds*/ .cast("kmp_desc_base_t") .access("ds_thread") /*__kmp_threads[t]->th.th_info.ds.ds_thread*/ .cast("kmp_thread_t").getRawValue(thread_id, 1);Reviewed By: @hbaeDifferential Revision: https://reviews.llvm.org/D100182