ClangJIT: Enhancing C++ with Just-in-Time Compilation · HackerPapers discussions

ClangJIT: Enhancing C++ with Just-in-Time Compilation — mentioned by DannyBee

Sat, 10 Aug 2019 05:35:42 GMT

I think you don't understand the goals Hal has, and lays out pretty explicitly in the paper (https://arxiv.org/pdf/1904.08555.pdf): 1. Be able to replace very complex template dispatch mechanisms with simple JIT ones. Your suggestion is not possible, because you can't compile it once (maybe you can compile it a ton of times though!) That is, unless someone has implemented a very very ridiculous set of dynamic detection and dispatch mechanisms, and your compiler supports changing microarchitecture/etc optimization per function or you split it out/ifdef it and compile the same file 5000 ways.…

Paper and discussion history. A mention is not an endorsement.

ClangJIT: Enhancing C++ with Just-in-Time Compilation — HN submission

Fri, 07 Jun 2019 15:06:14 GMT

ClangJIT: Enhancing C++ with Just-in-Time Compilation

11 points; 0 discussion replies on HN. Paper and source history. A submission is not an endorsement.

ClangJIT: Enhancing C++ with Just-in-Time Compilation — HN submission

Tue, 23 Apr 2019 09:47:06 GMT

ClangJIT: Enhancing C++ with Just-in-Time Compilation

1 point; 0 discussion replies on HN. Paper and source history. A submission is not an endorsement.

ClangJIT: Enhancing C++ with Just-in-Time Compilation — HN submission

Mon, 22 Apr 2019 20:26:09 GMT

ClangJIT: Enhancing C++ with Just-in-Time Compilation

12 points; 0 discussion replies on HN. Paper and source history. A submission is not an endorsement.

ClangJIT: Enhancing C++ with Just-in-Time Compilation — HN submission

Mon, 22 Apr 2019 07:33:13 GMT

ClangJIT: Enhancing C++ with Just-in-Time Compilation

12 points; 0 discussion replies on HN. Paper and source history. A submission is not an endorsement.