-
Notifications
You must be signed in to change notification settings - Fork 5
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
Failing to detect gcc for golden file regeneration #27
Comments
I am surprised to see a tolerance needed with ASTC images. The encoder is supposed to be invariant. But it appears it is not living up to the promise. What was your experience @aqnuep? |
That probably is the reason. Btw, which ASTC images do you see the need for tolerance? What test case are we talking about? |
I didn't see a need for tolerance. I was regenerating golden files dues to an update to the ASTC encoder and got the "... not updated ..." message. The tests in question are I don't know why there is an |
Ah, I believe this is related to some floating point precision differences we saw with the ASTC encoder when running on Apple silicon. |
As far as I can see the ASTC encoder is producing consistent results. It is the zlib deflator producing different results on x86_64 and Apple Silicon that requires use of |
I attempted to regenerate some golden files that have output tolerance enabled and got the message "... not updated on non-primary platform ..."
But I am running under Ubuntu 22.04 and using gcc 11 to compile. Possibly the reason for the failure is that my configuration after selecting "default compilers" shows
and if I run, e.g,
cc --version
the output iswhile for
gcc --version
it isso you can't see from either the CMake variables or --version output that it is really gcc.
The text was updated successfully, but these errors were encountered: