Demanded Abstract Interpretation (Extended Version) · HackerPapers discussions

Demanded Abstract Interpretation (Extended Version) — mentioned by moonchild

Sun, 21 Apr 2024 23:39:26 GMT

> repository of analyzed code yes, this is obviously what you want. there shouldn't be a notion of 'running' the compiler; it should simply be a persistent process. importantly, there are two issues, which are orthogonal but both critically important: iterativity—that is, produce an acceptable result immediately, but then continue to refine it—and incrementality—that is, when making a small change to the code, take advantage of information learned about the previous version. there is this recent paper on incrementality https://arxiv.org/pdf/2104.01270.pdf, though it has some caveats (e.g. it…

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

Demanded Abstract Interpretation (Extended Version) — mentioned by moonchild

Thu, 22 Feb 2024 21:51:35 GMT

'Compilers' should be incremental (and iterative), and the asymptotics are way more important than the constant factors; if the conceptual models are not adequate to effectively express very fine-grain incrementality, no amount of bitpacking is going to save you. https://arxiv.org/pdf/2104.01270.pdf as an example—this is not perfect, but very serviceable. Being able to serialise is good and valuable and useful, and enables some very interesting things, but you can still do a lot of useful things with just a persistent process working on in-memory structures.

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