[Octave-bug-tracker] [bug #51643] setting OMP_NUM_THREADS at runtime does not chaneg number of openmp threads

[Carnë Draug]

Follow-up Comment #4, bug #51643 (project octave):

> I hesitate to intercept and do special things for specific variables in
Octave's putenv function.
>
> Maybe we should document that the initial value of the number of threads may
be set from the environment and also offer a separate function to set the
thread limit for OMP? 

I am also unsure about catching special variables in setenv which is why I am
asking review here. However, I am also unsure about the potential for
confusion, even if documented, about the difference between OMP_NUM_THREADS,
the actual current number of openmp threads, and the number of threads to be
used by other processes that Octave may start.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51643>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/