In this case, I like the automagic system better, because other projects that link against OIIO have found it helpful to use thread.h. So I want it to be useful without somebody having to figure out all the strange cases of the build system, or if they didn't know what build options were used to generate the OIIO library they have installed.
On May 23, 2013, at 10:55 AM, Richard Shaw wrote: > On Thu, May 23, 2013 at 12:52 PM, Larry Gritz <[email protected]> wrote: > In gcc >= 4.8, do the old __sync_* intrinsics disappear, now that the > __atomic_* ones are present? > > Or are there particular platforms that never had the __sync but will have > __atomic under 4.8? > > Are we quite sure that on platforms that support both, that there is no > performance difference? > > Perhaps it would be better to implement this with some sort of definition > driven by a cmake option first rather than automagically? > > Richard > -- Larry Gritz [email protected]
_______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
