On 05.12.23 16:39, Andrew Stubbs wrote:
Hence, mentioning in this section in addition that
omp_low_lat_mem_space is honored on devices
seems to be the better location.
How about this?
LGTM – Thanks!
Tobias
--- a/libgomp/libgomp.texi
+++ b/libgomp/libgomp.texi
@@ -3012,9 +3012,9 @@ value.
On 04/12/2023 16:04, Tobias Burnus wrote:
On 03.12.23 01:32, Andrew Stubbs wrote:
This patch adds support for allocating low-latency ".shared" memory on
NVPTX GPU device, via the omp_low_lat_mem_space and omp_alloc. The
memory
can be allocated, reallocated, and freed using a basic but fast
al
Hi Andrew,
I now looked at the whole series - and the series LGTM,
except for some testcase issues, as outlined below.
First, I notice that there is no call to:
omp_destroy_allocator (gpu_lowlat);
While it might make sense to leave some of the testcases
without that call for testing purpose,
On 03.12.23 01:32, Andrew Stubbs wrote:
This patch adds support for allocating low-latency ".shared" memory on
NVPTX GPU device, via the omp_low_lat_mem_space and omp_alloc. The memory
can be allocated, reallocated, and freed using a basic but fast algorithm,
is thread safe and the size of the l
This patch adds support for allocating low-latency ".shared" memory on
NVPTX GPU device, via the omp_low_lat_mem_space and omp_alloc. The memory
can be allocated, reallocated, and freed using a basic but fast algorithm,
is thread safe and the size of the low-latency heap can be configured using
t
