I ran some more tests, and with proper CMake flags set for release, and decent optimization, the difference in code generation goes away. So it's gone. Thanks for the PR.
On Fri, Sep 30, 2016 at 5:30 PM, Larry Gritz <[email protected]> wrote: > I should also point out: it's a higher priority to remove it from public > headers, which are subject to the build flags and language mode of other > apps that use OpenEXR, than it is to remove it from OpenEXR's internals > which are only subject to OpenEXR's own build flags and rules. > > > > On Sep 30, 2016, at 5:09 PM, Larry Gritz <[email protected]> wrote: > > > > Don't let me bully you into removing it, if it really does something > useful for performance. > > > > But it will eventually disappear from the language, and it already (even > in C++11 mode, per current VFX Platform specs) is a deprecation warning, > which a lot of software build defaults intentionally turns into > full-fledged errors. > > > > Sorry about the duplicate PR, I should have scanned the list of pending > requests before submitting. > > > > > > -- > Larry Gritz > [email protected] > > > -- Ed Hanway R&D Supervisor // ILM // SF
_______________________________________________ Openexr-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/openexr-devel
