[Openmp-commits] [llvm] [openmp] [OpenMP] Add OpenMP extension API to dump mapping tables (PR #85381)
Krzysztof Parzyszek via Openmp-commits
openmp-commits at lists.llvm.org
Fri Mar 15 06:48:34 PDT 2024
================
@@ -16,28 +16,33 @@
#include "device.h"
/// Dump a table of all the host-target pointer pairs on failure
-void dumpTargetPointerMappings(const ident_t *Loc, DeviceTy &Device) {
+void dumpTargetPointerMappings(const ident_t *Loc, DeviceTy &Device,
+ bool toStdOut) {
MappingInfoTy::HDTTMapAccessorTy HDTTMap =
Device.getMappingInfo().HostDataToTargetMap.getExclusiveAccessor();
- if (HDTTMap->empty())
+ if (HDTTMap->empty()) {
+ DUMP_INFO(toStdOut, OMP_INFOTYPE_ALL, Device.DeviceID,
+ "OpenMP Host-Device pointer mappings table empty\n");
return;
+ }
SourceInfo Kernel(Loc);
- INFO(OMP_INFOTYPE_ALL, Device.DeviceID,
- "OpenMP Host-Device pointer mappings after block at %s:%d:%d:\n",
- Kernel.getFilename(), Kernel.getLine(), Kernel.getColumn());
- INFO(OMP_INFOTYPE_ALL, Device.DeviceID, "%-18s %-18s %s %s %s %s\n",
- "Host Ptr", "Target Ptr", "Size (B)", "DynRefCount", "HoldRefCount",
- "Declaration");
+ DUMP_INFO(toStdOut, OMP_INFOTYPE_ALL, Device.DeviceID,
----------------
kparzysz wrote:
The first argument to DUMP_INFO is named `toStdOut`, which suggests that it directs the message to be printed to the standard output. At the same time, the corresponding parameter name in the definition of DUMP_INFO is `always`, which looks like a conflict of intended meanings.
https://github.com/llvm/llvm-project/pull/85381
More information about the Openmp-commits
mailing list