-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows ISPC *For Consideration* #5166
Conversation
Most likely you want to use "--target=avx2-i32x16 --target=avx1-i32x16 --target=sse4.2-i32x8 --target=sse2-i32x8 --arch=x86_64" which is what is being used for Linux.. It compiles in all four and at runtime will select the one most appropriate based on the cpu. |
can you pull in my workflow change and to see if it builds on github |
I think I did what you asked .. |
Simple tests .. 5secs off of 60s render. |
You didn't merge in the GitHub action change to see if it compiles in github |
If it builds why not remove the the special "-ISPC" modifier and merge it, I can add the install code to the release and nightly action. If it works ship it. |
in a couple sequences I tried it decreased render time by 25%ish |
YOLO it, like the kids say |
Can the layering bug be affecting the performance here? If it doesn't process layers, it will be faster. I see your PR is compiled, I'll download and test it this afternoon. |
Its only the 2 render styles .. but sure it might have some effect on the results. |
I think the main thing left to update before merging is the README.windows. |
For discussions only .. This is my local code for running ispc - nothing special.
removed the #ifndef WXMSW and the updated the vs2022 project files.
One thing is ispc compiled for what?
ispc.exe "%(FullPath)" -o "$(IntDir)%(Filename).obj" --target=host
This compiles based on my PC's capabilities - do we need to set that to a value that is our now new low-bar for cpu requirements.
What was used on the mac size?