3adcf7e104
If numa-domains is used with num-places count, sometimes the function could create more places than requested and crash. This depended on the content of /sys/devices/system/node/online file, e.g. if the file contains 0-1,16-17 and all NUMA nodes contain at least one CPU in the cpuset of the program, then numa_domains(2) or numa_domains(4) (or 5+) work fine while numa_domains(1) or numa_domains(3) misbehave. I.e. the function was able to stop after reaching limit on the , separators (or trivially at the end), but not within in the ranges. 2021-10-18 Jakub Jelinek <jakub@redhat.com> * config/linux/affinity.c (gomp_affinity_init_numa_domains): Add && gomp_places_list_len < count after nfirst <= nlast loop condition. |
||
---|---|---|
.. | ||
alpha | ||
ia64 | ||
mips | ||
powerpc | ||
s390 | ||
sparc | ||
tile | ||
x86 | ||
affinity.c | ||
bar.c | ||
bar.h | ||
doacross.h | ||
futex.h | ||
lock.c | ||
mutex.c | ||
mutex.h | ||
omp-lock.h | ||
proc.c | ||
proc.h | ||
ptrlock.c | ||
ptrlock.h | ||
sem.c | ||
sem.h | ||
wait.h |