Re: Changing octave to exploit multi-core hardware

[John W. Eaton]

On 25-Mar-2008, Jaroslav Hajek wrote:

| A single OpenMP directive could do that, or even autoparallelization
| with some compilers,
| e.g. Intel C++. But there are two obstacles: first, the OCTAVE_QUIT
| macro (which breaks independence of cycles) and second, there is no
| guarantee that F has no side effects.

OK.  Suppose the function has no side effects (at least when compiling
with GCC, this property could be declared with the "pure" or "const"
attribute).  The OCTAVE_QUIT macro checks a global variable and calls
a function to handle an interrupt signal.  How should that be handled
if the loop is executing in parallel?

jwe