OClCollMeshEngn: collBuff only needs MAP_WRITE; silence dbg prints

When mapping in the collationBuff we only need to supply CL_MAP_WRITE
and not CL_MAP_WRITE_INVALIDATE_REGION since we don't care to
preserve the contents of the collation buff as input to the
collation kernel.
This commit is contained in:
2025-11-12 12:49:54 -04:00
parent 1dc74065fb
commit 96e64e24b8
2 changed files with 3 additions and 2 deletions
+2 -1
View File
@@ -1,5 +1,5 @@
// Debug macro: define DEBUG_COLLATE_DGRAMS to enable printf statements // Debug macro: define DEBUG_COLLATE_DGRAMS to enable printf statements
#define DEBUG_COLLATE_DGRAMS // #define DEBUG_COLLATE_DGRAMS
#ifdef DEBUG_COLLATE_DGRAMS #ifdef DEBUG_COLLATE_DGRAMS
#define DBG_PRINTF(...) printf(__VA_ARGS__) #define DBG_PRINTF(...) printf(__VA_ARGS__)
#else #else
@@ -49,6 +49,7 @@ __kernel void collate(
// Each PointXYZI is 4 floats (x, y, z, intensity) // Each PointXYZI is 4 floats (x, y, z, intensity)
#define FLOATS_PER_POINT 4 #define FLOATS_PER_POINT 4
uint collationBaseOffset = slotIndex * nPointsPerSlot * FLOATS_PER_POINT; uint collationBaseOffset = slotIndex * nPointsPerSlot * FLOATS_PER_POINT;
DBG_PRINTF("Running kernel: about to process points in slot.\n");
// Process based on data type using nested ifs (outer) with loops (inner) // Process based on data type using nested ifs (outer) with loops (inner)
if (dataType == 0) if (dataType == 0)
@@ -342,7 +342,7 @@ bool OpenClCollatingAndMeshingEngine::startCollateKernel(
mapAssemblyBuffer(CL_MAP_WRITE_INVALIDATE_REGION); mapAssemblyBuffer(CL_MAP_WRITE_INVALIDATE_REGION);
unmapAssemblyBuffer(); unmapAssemblyBuffer();
mapCollationBuffer(CL_MAP_WRITE_INVALIDATE_REGION); mapCollationBuffer(CL_MAP_WRITE);
unmapCollationBuffer(); unmapCollationBuffer();
// Validate buffers callable // Validate buffers callable