ID 533781 - OCIOColorSpace produces incorrect transforms for some negative colour values on certain CPUs creating artifacts

Problem summary:
OCIOColorSpace produces incorrect transforms for some negative colour values on certain CPUs
This affects both OCIO v1.0 and OCIO v2.1 configs. 

Customer reported version:
Nuke 14.0v2
 
Customer reported platform:
Windows 10
 
Steps to reproduce:
 
1) Open Nuke on a HP Z620 machine

2) Open the attached either attached Nuke script: OCIO_badTransform_OCIOv1.0.nk or OCIO_badTransform_OCIOv2.1.nk

3) View or render the OCIOColorSpace nodes, the outputs have incorrect results:

 
Expected behavior:
For the OCIOColorSpace node to output correct color values:

 
Actual behavior:
Some colors with negative values would end up with unexpected results
 
Workaround:
You may workaround the issue by setting the environment variable OCIO_OPTIMIZATION_FLAGS=0 to turn optimization off, or OCIO_OPTIMIZATION_FLAGS=20479 to set optimization to lossless. Additionally, setting OCIO_OPTIMIZATION_FLAGS=230440899 should workaround this issue, as long as the Nuke Viewer is not set to utilize the GPU. 

In the case where the ACES Studio config is being used switching from ACEScc to ACEScct also fixes the issue.
 
Reproduced by Support in:
Nuke 14.0v2 - Windows 10 - HP Z620 - Dual Intel Xeon E5-2680 0
Nuke 14.0v1 - Windows 10 - HP Z620 - Dual Intel Xeon E5-2680 0 - regression
 
Unable to reproduce bug in:
Nuke 13.2v5 - Windows 10 - HP Z620 - Dual Intel Xeon E5-2680 0
Nuke 14.0v2 - Windows 10 - HP Z840 - Dual Intel Xeon E5-2687W v4
Nuke 14.0v2 - CentOS 7 - Dell Precision 7820 - Dual Intel Xeon Gold 6134 CPU
Nuke 14.0v2 - macOS Monterey - Mac Studio - M1 Ultra
 
Earliest version tested
Nuke 13.2v5 - This issue doesn't appear in this version and has regressed on that hardware, other hardware may also reproduce the issue in Nuke 13.1