-
Notifications
You must be signed in to change notification settings - Fork 410
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
Fixes to AHB VUs and Tests #2014
Fixes to AHB VUs and Tests #2014
Conversation
Running through CI. |
Hey Spencer, on Android this passes on Pixel3 XL and NexusPlayer, but crashes on the GalaxyS10 and ShieldTV -- here's some loginfo: GalaxyS10 logcat:
ShieldTV logcat:
|
Thanks, the |
Running through CI. |
Same result, sorry. Lemme know if you need a copy of the log or anything like that.
|
sorry, I never actually pushed up my changes, been a slightly busier than normal this last week, will try to get to it soon |
51059be
to
736c10e
Compare
@mark-lunarg rebased and hopefully fixed both errors |
Running through the farm again. |
Galaxy S10 is still throwing up. Lemme know if you can use any other logs or info...
|
From internal Vulkan MR 3982, the VUID 4003 and 4005 should not have been added to start with and more information about it was added to the spec as well.
736c10e
to
7cf19a6
Compare
@mark-lunarg Finally got time to look back into this, should be good now 🙏 |
Sending through CI... |
Thanks Spencer! |
closes #2004
The first commit is a need dependency that removes
VUID-vkGetBufferMemoryRequirements-buffer-04003
VUID-VkBufferMemoryRequirementsInfo2-buffer-04005
From internal Vulkan MR 3982, it was decided these should never have been added (and will be gone in a future header now). I have written positive tests to prevent regression
Added positive test to check for export AHB from both a
vkBuffer
andvkImage
which caught the issue reported in #2004 from callingValidateInsertImageMemoryRange()
when it is an exportVkImage
AHB andallocationSize
is suppose to be0