Re: OpenMP, OMP_NUM_THREADS and putenv - not working as expected.

[Guido Walter Pettinari]

Hi John!

Thank you for your answer. All the parallelization in my code is made with 
standard C++ & GSL types.
No use of Octave libraries is made apart from the oct-file wrapper to the 
functions, which plays around
only with input & output. So far everything went perfectly fine.

@Chi Chan
I am using gcc-4.2.1 (the one shipped with Mac Os X 10.6) and Octave 3.2.3. My 
oct-files are 32-bit.

Cheers,

Guido

On Apr 20, 2010, at 1:59 , John W. Eaton wrote:

> On 19-Apr-2010, S ren Hauberg wrote:
> 
> | man, 19 04 2010 kl. 01:19 -0800, skrev coccoinomane:
> | > Hi Soren!
> | > 
> | > Thank you for your answer.
> | > 
> | > > I hope you realise that Octave itself is not thread-safe. 
> | > 
> | > Does it mean that, in all cases, it is dangerous to run an oct-file with
> | > OpenMP parallelization?
> | 
> | No, but it means that we don't even attempt to give you any garanties.
> | Many operations are probably already thread-safe, but if you want to be
> | sure, you really need to look at the actual implementation.
> 
> If your function does some multi-threaded thing that is compltely
> independent of Octave's internals, I would guess you are OK (assuming
> the multi-threaded code you call is actually thread safe).  But if you
> make calls back to the Octave internals, there are no guarantees as
> the code in the Octave libraries is not thread safe.
> 
> jwe