On 2024-02-29 6:02 p.m., Thomas Schwinge wrote:
Hi!
On 2024-02-01T19:20:57+0000, John David Anglin <d...@parisc-linux.org> wrote:
Tested on hppa-unknown-linux-gnu. Committed to trunk.
Set num_threads to 50 on 32-bit hppa in two libgomp loop tests
We support a maximum of 50 threads on 32-bit hppa.
What happens if you go higher? Curious, what/why is that architectural
limit of 50 threads?
One gets an EAGAIN error at 51. I don't know why 50 is the architectural limit
on hppa-linux.
I had asked Helge previously but didn't get an answer. As far as I can tell,
limit isn't set by glibc.
It seems 64 is supported on all other targets.
I wonder: shouldn't that cap at 50 threads happen inside libgomp,
generally, instead of per test case and user code (!)? Per my
understanding, OpenMP 'num_threads' specifies a *desired* number of
threads; the implementation may limit that value.
Sounds like a good suggestion.
Dave
--
John David Anglin dave.ang...@bell.net
