Luke Gorrie

@igelhaus I am still not making the connection. On the one hand I do see that NaN-tagging requires tagged values to be encoded in a specific way. On the other...

@igelhaus Oh, on reflection I believe you are right. I was thinking too much in terms of the NaN-tagged value representation where the `itag` field is valid. Of course the...

Braindump on some of the issues involved here: Goal is to allow sunk values to escape from trace *Source* to linked trace *Target*. Target is a root trace and Source...

I also reflect that there might be some holes in this scheme that undermine its value. Ideally I would like application programmers to feel comfortable assigning 64-bit integers and pointers...

@javierguerragiraldez I would love your feedback on this feature idea!

@javierguerragiraldez Thanks for explaining that. The backend you are using for LOOM does seem very pragmatic. You keep the implementation lean by reusing all the existing code; deferring analysis to...

> What events would be logged? Good question! Start with the same events that LuaJIT logs now. Just having this available in production would be a massive win. Then I...

@fsfod Thanks for sharing your work! I like the way you have defined a clear ABI for your low-level trace logs. I am thinking about how this approach could fit...

... Incidentally, I wonder whether the `jit.util` introspection interface could be built on top of the @fsfod ABI? In that case tools like LOOM and `jit.v` and `jit.dump` could be...

So @fsfod @javierguerragiraldez I wonder if this would be a reasonable position for RaptorJIT to take: - Remove `jit.attach()` and `jit.util()` completely. - Add extensive binary logging in the native...