Closed lbarbieri closed 8 years ago
Ok this is a bug. We should assume xmm_enabled=true when the XSAFE feature is not present.
Could you please verify that it also works for your machine when you initialize "bool xmm_enabled=true;" at its declaration.
Hi Sven - thanks for your response.
Yes - making that change worked.
Thanks for reporitng the issue. I also verified that is works on an older machine. I updated the v2.7.1 release with that fix, as the issue is quite serious. Just make a git pull and you should get the updated v2.7.1 tag.
Thanks very much!
Hello,
I'm running Embree v2.7.1 on a CPU that supports SSE (2, 3, 4.1, 4.2) however I get error message "CPU does not support SSE2" along with an exception having this stack trace:
However Embree previously ran fine on this exact hardware as of v2.6.2.
It looks like
getCPUFeatures()
is requiringOS-enabled XSAVE/XSTOR
to be present for any SSE support to be detected (which is failing for my processor - CPUID data given below), but I believe this requirement to be unnecessary.Just to test, I disabled the XSAVE/XSTOR requirement for SSE detection, and things seemed to run OK. Here's what I did:
(I don't know if this is the right way to do this, just wanted to see if things would run.)
Any feedback on this issue would be appreciated.
Thanks for your time! Lou
Platform information
Following is some info describing the machine I'm running upon.
Embree info
Please note that the SSE ISAs are only showing-up because I hacked-around this issue (as noted above) so I could run.
CPUID (raw flags)
Of interest is (at least) the line for
0x00000001
.CPUID
Of interest are that all
SSE
features are supported, but neitherOS-enabled XSAVE/XSTOR
norXSAVE/XSTOR states
are.