I think the interesting point is that Chris is trying to run on a reduced environment that doesn't fully conform to the spec. That's very typical for embedded systems and older game consoles. Modifying the compiler or runtime in those situations is seldom desirable and possibly impossible. There might not even be signals available to trap exceptional conditions, so Chris' approach to ignore the test failures is probably the only viable option, as modifying OpenEXR to deal with such stripped environments seems way out of scope. He'll need to battle harden his application instead.
Sent from my iPhone On May 29, 2014, at 12:14, "Christopher Horvath" < address@hidden> wrote: I'm compiling OpenEXR with exceptions, but the libraries that I am required to link to beneath OpenEXR have the exception behavior disabled (inconsistently).
I'm happy with the results that 2.1.0 passes all the regular tests for all the libraries. The fuzz tests don't work, but in my case, that's okay, I think.
|