Jérôme Carretero on Nostr: nprofile1q…6gyrf nprofile1q…e0kak Excluding obvious shader stuff and regexp, on ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqf3nlrmpjja65pzmvlegyl27l0y2m007nncxttdwqndrejajvdzask6gyrf (nprofile…gyrf) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqu7eu2j3ytu686e0dp984rqn2kedylkz2k7qlvxvshdg67h77f3aq9e0kak (nprofile…0kak)
Excluding obvious shader stuff and regexp, on the top of my head there are some OpenCL libs (eg. clFFT) generating specialized code, there's llvm-based stuff like Halide, I recall the FFTW library being mixing codelets at runtime when preparing plans. The gcc JIT is also invoking gcc to create ldopen dynamic libraries based on generated code, not sure it really counts as a JIT.
Excluding obvious shader stuff and regexp, on the top of my head there are some OpenCL libs (eg. clFFT) generating specialized code, there's llvm-based stuff like Halide, I recall the FFTW library being mixing codelets at runtime when preparing plans. The gcc JIT is also invoking gcc to create ldopen dynamic libraries based on generated code, not sure it really counts as a JIT.