#asahi-gpu · 2021-04-17 12:00
glibcoh, they don't use a fast sin at all? That's interesting indeed#asahi-gpu · 2021-04-16 21:49
glibcprecise sin is expensive, there's no getting around that (either instruction, or LUT)#asahi-gpu · 2021-04-15 21:43
glibcwith early-z, no alpha-to-coverage or other weird features#asahi-gpu · 2021-04-15 21:42
glibcthat appears even in empty fragment shaders#asahi-gpu · 2021-04-15 21:42
glibc# 48 00 C2 00 -unk48 h0, 2l, u0l.neg#asahi-gpu · 2021-04-11 18:21
glibcDarkShadow44: thanks :)#asahi-gpu · 2021-04-11 18:11
glibctaking humble baby steps, but yeah#asahi-gpu · 2021-04-11 18:05
glibccool, that's exactly what I wanted. (I was still missing a clean method for extracting the raw payload)#asahi-gpu · 2021-04-11 18:03
glibcno, I wasn't aware of this -- but this looks quite nice :) Thanks for the link.#asahi-gpu · 2021-04-11 17:51
glibcI wanted a .metal -> .disasm workflow, which I now have :)#asahi-gpu · 2021-04-11 16:33
glibcI guess I can build an binary archive and serialize it, but I wonder if there is an easier way to get the raw compiled binaries.#asahi-gpu · 2021-04-11 14:51
glibcramping up on Metal... I can compile .metallib files, which I understand are LLVM IR containers. I can compile them in a metal app; how can I get the output binary?#asahi-gpu · 2021-04-10 17:02
glibcalright :)#asahi-gpu · 2021-04-10 17:01
glibchow about having a function-local array, dynamically indexed by a uniform/attribute?#asahi-gpu · 2021-04-10 16:42
glibcactually what bothers me is the 372/388 boundary :) 20/36 -> computation could simply be in unit of 32 bytes#asahi-gpu · 2021-04-10 16:39
glibcah, the input number is TLS byte size in shader?#asahi-gpu · 2021-04-10 16:05
glibc@bloom: thank you for your suggestion. I will have a look.#asahi-gpu · 2021-04-10 12:07
glibceither GPU reverse engineering, or driver work#asahi-gpu · 2021-04-10 12:03
glibcthanks#asahi-gpu · 2021-04-10 11:10
glibcDo you have suggestions of "relatively" easy tasks to help the project?