-
Notifications
You must be signed in to change notification settings - Fork 123
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
Remove block_index from thread data #1746
base: dev
Are you sure you want to change the base?
Remove block_index from thread data #1746
Conversation
CI gfxreconstruct build queued with queue ID 258618. |
CI gfxreconstruct build # 4848 running. |
CI gfxreconstruct build # 4848 failed. |
CI gfxreconstruct build queued with queue ID 259014. |
CI gfxreconstruct build # 4857 running. |
CI gfxreconstruct build # 4857 passed. |
The current use case is to do something in a Vulkan layer upchain of GFXR, marking before calling downchain and then marking after calling downchain with the the block number. In order to exactly correspond to the command just called, having the block number in the thread seems to make the most sense. Would this PR break that expectation? |
a6e5a0c
to
4162f8d
Compare
CI gfxreconstruct build queued with queue ID 277507. |
CI gfxreconstruct build # 5051 running. |
CI gfxreconstruct build # 5051 failed. |
No description provided.