Skip to content
This repository has been archived by the owner on Jul 19, 2018. It is now read-only.

Validation layer reports errors if memory object alias same memory #328

Closed
misojarv opened this issue Apr 13, 2016 · 3 comments
Closed

Validation layer reports errors if memory object alias same memory #328

misojarv opened this issue Apr 13, 2016 · 3 comments
Assignees
Labels
Milestone

Comments

@misojarv
Copy link

Memory objects are allowed to alias. See "11.8 Memory Aliasing" in the spec.

Triggered by CTS tests:
dEQP-VK.memory.pipeline_barrier.*

@lentinem
Copy link

Please post the error you found.

@lentinem lentinem added this to the P2 milestone Apr 13, 2016
@misojarv
Copy link
Author

The error messages are:
"ERROR: Buffer 33d7f30 is alised with image 33f2fc0 (code 0x00000003 at Buffer:0)"
"ERROR: Image 3426160 is alised with buffer 33d7f30 (code 0x00000003 at Image:0)"

The test case does make sure that they are never used at the same time and that correct pipeline barriers are used.

@mark-lunarg
Copy link
Collaborator

Aliasing memory objects will no longer result in validation errors. #1264 has taken care of this for the most part.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants