+20

TODO.md

reviewed

··· 1 1 + # Shader Compiler 2 2 + Infinite number of issues and to be fixed. 3 3 + 4 4 + # Shader API 5 5 + [] Before we actually support spir-v or something similar, we 6 6 + need a way for applications to specify shader code. I like the 7 7 + GIR api and I believe it would be epic if we could expose something 8 8 + akin to that to the user; this simplifies things like JIT-GPU code, 9 9 + I cannot see why you wouldn't allow this really. 10 10 + 11 11 + # Semaphores 12 12 + I think there are two levels of semaphores inside mesa; both internal driver 13 13 + semaphores and also user-provided ones. I think none of them work, we want both 14 14 + to work :^) 15 15 + 16 16 + # Crashes & Hangs 17 17 + [] I manage to hang my machine easily by writing incorrect shaders. I have not 18 18 + experienced this before in Vulkan; i believe the driver detects a hang and 19 19 + restarts the device. However, we are doing something wrong, so my machine 20 20 + fails to restart.

+3

test/examples/07_hello_dispatch/hello_dispatch.cpp

reviewed

··· 10 10 11 11 auto sem = kes_create_semaphore(dev, 0); 12 12 13 13 + ((uint32_t *)x.cpu)[0] = 1; 14 14 + ((uint32_t *)x.cpu)[2] = 4; 15 15 + ((uint32_t *)x.cpu)[3] = 10; 13 16 printf("x: %p %p\n", (void *)x.cpu, (void *)x.gpu); 14 17 15 18 auto compute = kes_create_queue(dev, KesQueueTypeCompute);