David Livshin <[EMAIL PROTECTED]> writes:

> I thought that "gcc" mailing list is appropriate as I need this
> information in order to implement auto-parallelizer for the
> gcc-generated code. How the gcc-supported parallelizer (
> "-ftree-parallelize-loops=n" ) treats the calls to library routines?

Sorry, I didn't realize that this was directly connected to gcc
development.  Within gcc, see gcc/builtins.defs.  A function which is
marked const or pure is thread-safe by definition.  Otherwise the
function must be presumed to be not thread-safe.

Ian

Reply via email to