<abbe>
^^ from truss(1)-ing it seems it's waiting on this
<brixen>
yorickpeterse: cool article
<brixen>
abbe: hm, seems like it may not be canceling the timer on shutdown
<brixen>
abbe: I have a freebsd 10 vbox machine, what version are you running?
<abbe>
I'm running on 9.3 (amd64)
<brixen>
would it be possible for you to test on 10?
<brixen>
checking vagrantbox.es for a 9
<yorickpeterse>
brixen: there's this part where it starts talking about how to implement C++ exception handling in the IR
<abbe>
Sure, I can try, let me find a 10.x host
<brixen>
looks like there's a 9.2 minimal available
<yorickpeterse>
my jaw dropped at the amount of IR required for that
<yorickpeterse>
"and here's a bucket load of LLVM IR, have fun"
<brixen>
yorickpeterse: yeah, the IR is really low
<brixen>
hence, the work we discussed :)
<yorickpeterse>
"we need to fix that" :P
<brixen>
heh
o0oo0o has quit [Ping timeout: 250 seconds]
<brixen>
so, the interesting thing was hearing Chris L say they built a new IR above LLVM IR for Swift
<brixen>
it's been obvious to evan and I that is needed, but no validation quite like hearing Chris L say it :)
<yorickpeterse>
I can imagine, looking at LLVM it's not exactly the most convenient thing to start with
<brixen>
abbe: I'll download this 9.2 box
<abbe>
thanks in advance
<abbe>
brixen: i've a port, if you prefer that
<brixen>
abbe: what command should I run to upgrade it to 9.3? or is that possible?
<abbe>
freebsd-update upgrade -r 9.3-RELEASE
<yorickpeterse>
Still, my main concern is I have literally no idea where to start. Even the Kaleidoscope tutorial is a lot to digest for somebody new to compilers
<brixen>
abbe: ok, thanks
* abbe
maintains lang/rubinius port
<brixen>
yorickpeterse: we're going to work on that :)
<brixen>
abbe: oh awesome, thank you!
<yorickpeterse>
My idea was to basically work my way through our JIT, top to bottom, while reading up on all the related LLVM constructs
<abbe>
thank you! :-)
<yorickpeterse>
That way I have at least some context
<yorickpeterse>
But that will take quite some time
<yorickpeterse>
Might actually have to take some time off for that around December
<brixen>
yorickpeterse: yeah, it would
<yorickpeterse>
or just strap myself to a chair and force myself to work through the tutorials/docs
<yorickpeterse>
I do see a lot of potential in smacking Rbx on top of that
<yorickpeterse>
Kinda like Parrot, without inventing the underlying stuff ourselves
<brixen>
abbe: I probably won't be able to debug this today, though
<abbe>
brixen: no problems, i'll get back to you results with 10.x
<brixen>
ok, thanks
<yorickpeterse>
abbe: for the sake of not losing track of this, could you submit this as an issue on Github?
<yorickpeterse>
abbe: with OS info, and stacktraces if there are any
brixen is now known as brixen_pomodoro
<yorickpeterse>
oh boy
<yorickpeterse>
brixen_pomodoro: does this mean you'll only be connected to IRC for 25 minutes, followed by a 3 minute downtime? :P
<brixen_pomodoro>
hah
<brixen_pomodoro>
inverse
<yorickpeterse>
Pomodoro works great by the way, though I always forget to start my timer