This is the mail archive of the
mailing list for the GCC project.
Re: libgomp: Thread creation failed: Invalid argument
- From: Tim Schmielau <tim at physik3 dot uni-rostock dot de>
- To: Asher Langton <langton2 at llnl dot gov>
- Cc: gcc at gcc dot gnu dot org, Diego Novillo <dnovillo at redhat dot com>
- Date: Tue, 15 Aug 2006 18:03:18 +0200 (CEST)
- Subject: Re: libgomp: Thread creation failed: Invalid argument
- References: <email@example.com>
On Tue, 15 Aug 2006, Asher Langton wrote:
> Tim Schmielau wrote on 08/15/06:
> > The problem appears for any OMP_NUM_THREADS value other than 1 (I tried
> > up to 8 on an 8-way machine).
> > Extracting a testcase from the 18.000 lines of code will probably require
> > some work, so I was looking for easier things to chek first. But I'll try
> > to do that, then.
> Are you using a lot of threadprivate variables? Try setting the
> GOMP_STACKSIZE environment variable to a large value (in kB) and see
> if the problem persists.
Yes, I do use a large set of threadprivate variables.
I tried different settings of GOMP_STACKSIZE before. However, I somehow
didn't hit a working setting as I didn't know it was measured in kB.
The program now works on x86_64 with SETENV GOMP_STACKSIZE 1048576.
On i686 I do not find a working stacksize, as for too large stacksizes the
program dies with a segfault. Wonder how PGI and ifort deal with the
limited address space.
Thanks a lot!