-
Notifications
You must be signed in to change notification settings - Fork 404
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
AVX Feature Detection in GCC Release corrupts something (but what?) #4506
Comments
Compilers... |
Very useful thanks. I will take a peek |
1. Rename namespace Surge::UI to Surge::GUI 2. For now make gcc implementation of hasAVX() return true since it crashes the about box. Addresses surge-synthesizer#4506
OK I'm pushing a workaround for this and re-naming this issue to the root cause. More in a second. |
1. Rename namespace Surge::UI to Surge::GUI 2. For now make gcc implementation of hasAVX() return true since it crashes the about box. Addresses surge-synthesizer#4506
1. Rename namespace Surge::UI to Surge::GUI 2. For now make gcc implementation of hasAVX() return true since it crashes the about box. Addresses #4506
Got it. merge shortly. |
@baconpaul editing this issue at the top
Basically a release build of xt blows up on the about screen. The reason is because the about screen asks if the cpu has AVX support to decorate the about info. For some reason gcc release code and our implementation of hasAVX corrupts memory somehow (how?). So for now I made hasAVX always return true. But clearly this isn't OK and we need it to actually detect without blowing up stuff so renaming this issue and leaving it open.
This is the command line output for Debug that can open About screen
and for Release that segfaults when About is opened (you can see I opened and closed it twice)
The text was updated successfully, but these errors were encountered: