vkcubepp: Support protected output#1078
Conversation
|
Author gnoliyil not on autobuild list. Waiting for curator authorization before starting CI build. |
1 similar comment
|
Author gnoliyil not on autobuild list. Waiting for curator authorization before starting CI build. |
|
|
This change was originally introduced into Fuchsia's Vulkan-Tools fork in https://fxrev.dev/c/third_party/Vulkan-Tools/+/444614. If `--protected_output` command line option is specified, vkcubepp will render to the protected memory. Bug: https://fxbug.dev/378964821 Change-Id: I11c89d3d722236448edd41ca51a03f80d0ba7324
gnoliyil
force-pushed
the
protected_output
branch
from
d2cfe86 to
8fd8c03
Compare
|
Author gnoliyil not on autobuild list. Waiting for curator authorization before starting CI build. |
1 similar comment
|
Author gnoliyil not on autobuild list. Waiting for curator authorization before starting CI build. |
|
CI Vulkan-Tools build queued with queue ID 377419. |
|
CI Vulkan-Tools build # 1627 running. |
|
CI Vulkan-Tools build # 1627 failed. |
|
#1079 (vkcubepp: Support Fuchsia) has been merged since last review. I uploaded a new version of this PR to include the Fuchsia-specific manifest files to run the tests in protected mode on Fuchsia. Please take a look? |
charles-lunarg
left a comment
charles-lunarg
left a comment
There was a problem hiding this comment.
Apologies for the delay, Vulkanized took over my schedule for a bit, and I've been working through the backlog ever since.
4 participants
This change was originally introduced into Fuchsia's Vulkan-Tools fork in https://fxrev.dev/c/third_party/Vulkan-Tools/+/444614.
If
--protected_outputcommand line option is specified, vkcubepp will render to the protected memory.Bug: https://fxbug.dev/378964821