-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[vulkan] performance_wrap test results don't match #7559
Comments
derek-gerstmann
pushed a commit
that referenced
this issue
May 9, 2023
steven-johnson
pushed a commit
that referenced
this issue
May 10, 2023
…atch (#7560) * Fix missing initializer for vulkan memory config that got munged in a previous merge. This gets the correctness_multiple_outputs test to pass. * Disable test for Vulkan since shared memory results are incorrect (see issue #7559) * Clang tidy/format pass --------- Co-authored-by: Derek Gerstmann <dgerstmann@adobe.com>
ardier
pushed a commit
to ardier/Halide-mutation
that referenced
this issue
Mar 3, 2024
…atch (halide#7560) * Fix missing initializer for vulkan memory config that got munged in a previous merge. This gets the correctness_multiple_outputs test to pass. * Disable test for Vulkan since shared memory results are incorrect (see issue halide#7559) * Clang tidy/format pass --------- Co-authored-by: Derek Gerstmann <dgerstmann@adobe.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There appear to be some incorrect results in the performance_wrap test for shared memory that need investigating:
The text was updated successfully, but these errors were encountered: