3 ms·
Wow this is amazing! I wish I'd known about this when I was trying to hack an optimization into a fork of GCC in undergrad years! What really excites me though
by sakras 4y ago
Wow this is amazing! I wish I'd known about this when I was trying to hack an optimization into a fork of GCC in undergrad years!
What really excites me though is this: I've frequently noticed a big tradeoff libraries make between ease-of-use and efficiency. For example, pimpling everything to make the API consistent. This isn't particularly efficient, but it's done to make the library easier to use. Similarly with lots of other interfaces that might incur tons of random little heap allocations to make it convenient to write the usage code.
Now imagine a future where library writers ship plugins with library-specific optimizations/rewrites. Suddenly, you can get the best of both worlds: nice interfaces and none of the overhead.
Anyone know if Clang supports something like this? Is there any work on a standard compiler plugin interface?