Luke Gorrie

Results 438 comments of Luke Gorrie

I would love some feedback on this formulation re: understandability, accuracy, usefulness, etc.

I am experimenting with putting the "Loops and Patches" concept directly into the tooling now. Consider this simple program: ``` function see (value) x = value end function test ()...

Getting the short summaries of traces right is quite hard. I had been thinking it would be nice to write things like: ``` trace 1 loop at Mod:init:3 trace 2...

Is it reasonable to say that lambda-lifting would be a feature of the bytecode compiler rather than the JIT? Since the bytecode compiler is a single-pass C program I am...

Generally there should be a disclaimer somewhere the the current compiler is quite simple and literal. If you are using it as an intermediate representation for a compiler you should...

> wow! ive thought that Mike is invisible, i didnt find the talk, does it have a record? id like to see the legend! Here's the only historical record that...

Thanks for reporting! Could you make this a pull request with a fix please, since you know the solution, and we can merge it?

I tried to remove REF_BIAS. This turned out to be tricky. On the one hand it seems innocent to switch trace IR references from unsigned to signed numbers. On the...

Snabb's approach is to use multiple single-threaded processes e.g. one for each CPU core that you want to use. Then coordinate these processes using the minimum necessary interaction via IPC...

NB: ljsyscall makes it easy to use all the right system calls to fork children, react to process failures, perform out-of-process cleanup, etc. The Snabb implementation is [worker.lua](https://github.com/snabbco/snabb/blob/master/src/core/worker.lua).