PixelyIon 07d45ee504 Introduce FenceCycle Chaining ... If we want to allow submitting multiple pieces of work to the GPU at once while still requiring CPU synchronization, we'll need to track all past fence cycles associated with a resource alongside the current one. To solve this the concept of chaining fences has been introduced, fences from past usages can be chained to the latest fence which'll then recursively forward operations to chained fences. This change also ends up mandating a move away from `FenceCycleDependency` as it would prevent fences from concurrently locking the same resources which is required for chaining to work as two fences being chained fundamentally means they're locking the same resources. The `AtomicForwardList` is therefore used as the new container.		2022-08-06 22:18:42 +05:30
..
libraries	Remove PugiXML submodule	2022-07-26 20:16:24 +05:30
src/main	Introduce FenceCycle Chaining	2022-08-06 22:18:42 +05:30
.gitignore	libNX FS Initalization (v0.3)	2019-10-18 16:22:38 +05:30
build.gradle	Only set hasFragileUserData for signed builds	2022-08-06 22:18:42 +05:30
CMakeLists.txt	Add utilities for reading and installing gpu driver packages	2022-08-06 22:00:19 +05:30
proguard-rules.pro	Add kotlinx.serialization-json dependencies	2022-08-06 22:00:19 +05:30