github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm
Set by AlexDaniel on 12 June 2018.
nine brrt: I'd be grateful for any such hints! My understanding of the JITs control flow is limited 07:15
tellable6 nine, I'll pass your message to brrt
Guest38485 is everyone working on adventofcode.com/2019 ? 12:54
nwc10 Guest38485: domm mentions it every so often on #austria.pm over on irc.perl.org 14:59
nine Guest38485: I don't need advent calendar puzzles. MoarVM supplies me with a steady flow of the greatest puzzles and mysteries that want solving :) 15:12
dogbert17 nine: have you solved the JIT puzzle yet? 17:10
nine dogbert17: no, still on it 17:14
dogbert17 nine: any wise comments from jnthn or brrt? 18:27
nine not yet 18:58
nine No progress today :/ 20:48
I do have some suspicion...that tc->cur_frame ends up pointing to the wrong frame as it never had a spesh_cand but we're in JITed code anyway 20:51
nine That tc->cur_frame gets set by NativeCall's callback handler: tc->cur_frame = backup_cur_frame; 20:56
I.e. that's the frame that called the native code that ran the callback 20:57
jnthn nine: Hmm...I wonder if it could be something like a deopt all causes an uninlining, creating a new top frame, and then it restores backup_cur_frame to the wrong thing. That doesn't quite match the symptoms though... 23:44