Our great sponsors
-
In my own compiler, depending on how you count, the program goes through at least six representations. Each compilation target may also use different representations after the middle-end. I would like to have even more, but my implementation language (Haskell) and perhaps my own lack of skill makes it infeasible to trivially define new IRs that are small variants of a previous one (65 lines is the current lower bound for a representation that doesn't have anything interesting going on - but the line count increases quickly once you want custom IR nodes).
-
The language itself is here. I've added a section at the end which lists the special options that can be used to display the generated PCL, MCL and other internal structures, if you manage to run it (you will need Windows). These are otherwise not documented.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Related posts
- What downsides exist to Futhark? Seems almost too good to be true?
- GPU Programming: When, Why and How?
- Functional GPU programming: what are alternatives or generalizations of the idea of "number of cycles must be known at compile time"?
- The Futhark Programming Language: Functional Array Programming in CUDA
- Achieving High-Performance the Functional Way