4 ms·
are you sure about the practical implications? Quoting the abstract: "At the moment, Lisp programs running on CPUs outperform Lisp programs on GPUs"
by actondev 7y ago
are you sure about the practical implications?
Quoting the abstract:
"At the moment, Lisp programs running on CPUs outperform Lisp programs on GPUs"
- dTal 7y agoYou're right it seems - as written, the parsing overhead from the requirement to make the entire system run the GPU makes it impractical. A hybrid system could outperform CPU or GPU alone. What I really want is a scheme->GLSL shader compiler - much narrower and more tractable.
- jakeogh 7y agoThis is likely unrelated, but your comment makes me think of clasp: https://github.com/clasp-developers/clasp https://github.com/clasp-developers/clasp
- ohpauleez 7y agoIn case you haven't seen the applications of nanopass compilers to do similar things, specifically harlan, here you go: https://github.com/eholk/harlan https://github.com/eholk/harlan
- BubRoss 7y agoWhat would it give you to compile scheme to glsl? Glsl is already a pretty direct yet high level representation of shaders. Why put another layer on top of it?
- absrnd 7y agoCheck out Hypergiant (Scheme -> GLSL) http://wiki.call-cc.org/eggref/4/hypergiant http://wiki.call-cc.org/eggref/4/hypergiant or CEPL (common lisp -> GLSL) https://github.com/cbaggers/cepl https://github.com/cbaggers/cepl