Camelia, the Perl 6 bug

IRC log for #moarvm, 2013-07-04

| Channels | #moarvm index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:18 benabik joined #moarvm
00:48 benabik joined #moarvm
01:27 woosley joined #moarvm
04:48 birdwindupbird joined #moarvm
05:30 FROGGS[mobile] joined #moarvm
05:46 FROGGS[mobile]2 joined #moarvm
06:08 FROGGS joined #moarvm
06:21 arnsholt joined #moarvm
09:08 jlaire joined #moarvm
09:13 yoleaux joined #moarvm
09:27 itz joined #moarvm
09:27 jnthn_ joined #moarvm
09:27 pmichaud_ joined #moarvm
09:31 tokuhirom_ joined #moarvm
09:32 timotimo joined #moarvm
09:40 woosley joined #moarvm
10:04 not_gerd joined #moarvm
10:04 * not_gerd just submitted https://github.com/MoarVM/MoarVM/issues/41
10:04 * jnthn just replied :)
10:05 nwc10 is it possible/is it sane/is it easy to get a github bot to announce new issues to channel?
10:05 not_gerd jnthn: great
10:06 jnthn not_gerd: Thanks for creating the issue, so we can track that one. :)
10:15 sorear nwc10: dalek used to have that functionality, but then github made incompatible changes to the issues API and dalek was never updated
10:52 not_gerd left #moarvm
13:43 woosley1 joined #moarvm
13:50 benabik joined #moarvm
16:45 FROGGS joined #moarvm
19:37 BinGOs_ joined #moarvm
19:39 Util_ joined #moarvm
19:39 rblackwe joined #moarvm
19:43 BinGOs joined #moarvm
19:54 BinGOs_ joined #moarvm
19:56 TimToady_ joined #moarvm
19:58 BinGOs joined #moarvm
20:04 ssutch joined #moarvm
21:34 Guest1337 joined #moarvm
21:55 diakopter jnthn: u around?
21:56 jnthn diakopter: yeah
21:56 jnthn In the midst of debugging stuffs...
21:56 diakopter jnthn: do you know whether nqpj can cross-compile on moar?
21:57 jnthn Can we use nqp-jvm for the Moar build?
21:57 diakopter right, that's what I'm asking
21:57 diakopter setting up a new dev environment
21:57 diakopter not wanting to install parrot
21:58 diakopter well, setting up 2 new dev environments, really
21:58 diakopter one in windows; one in mac os x
21:58 diakopter lizmat: btw you convinced me to get a retina
21:59 diakopter how long has ActivePerl been non-zero-price for production/business use?
21:59 lizmat it's always good to have a retina if you want to look :-)
21:59 jnthn diakopter: No, we can't 'cus re-using the MAST -> bytecode compiler is done through a Parrot dynop.
21:59 diakopter oh yeah, that.
22:00 diakopter well, that's something to work on I could do I guess
22:00 diakopter (integrate compiler.c into moarvm/nqp)
22:01 diakopter jnthn: do you have a hint of where to start there?
22:01 diakopter (I'm guessing forking compiler.c to start)
22:01 jnthn I wrote compiler.c with a load of macros. In theory, we "just" need to define them.
22:01 jnthn For Moar.
22:01 diakopter right, I've done it before
22:02 diakopter you probably have forgotten :P
22:02 jnthn Then some kinda compile op, I guess.
22:02 jnthn Yes, probably ;-)
22:02 diakopter I made that tiny perl-ish expression/statement/assembly language not-quite-not-quite-perl
22:02 jnthn I guess it can get a hash of the various types it wants to know about rather than loads of operands.
22:02 jnthn And a tree.
22:02 jnthn ah, yes ;)
22:03 diakopter tested a couple of the edge cases of the bytecode compiler
22:03 jnthn Anyway, doing that will be one thing off the "what we need to bootstrap" roadmap
22:03 diakopter like number of constants, strings, code size, etc
22:03 diakopter yeah
22:03 cognominal joined #moarvm
22:04 diakopter let's see, a hash of the types
22:04 diakopter (you said)
22:04 jnthn yeah
22:04 diakopter (and the mastree)
22:04 jnthn 'cus it needs to know MAST::Op, MAST::Label, etc.
22:05 diakopter (btw, I was poking fun at myself earlier because *I* had completely forgotten I'd redone the macros for compiler.c before)
22:24 diakopter jnthn: help me remember what compiler.c would need to do with the type objects (are they not accessible from the WHAT of the tree nodes)?
22:25 jnthn They're to identify what type of node we have.
22:26 diakopter theoretically you could look up their names and cache them the first time to get the pointers, but yeah
22:29 jnthn Look up...where? :)
22:30 diakopter I thought those nqp type objects stored their names somewhere
22:30 diakopter (on themselves)
22:30 jnthn Hm...guess in the meta-object...
22:30 jnthn But it's more robust to pass 'em in, I think.
22:30 diakopter k
23:05 Guest1337 joined #moarvm
23:12 diakopter jnthn: how would the moarvm compile op help the nqpj running in the jvm
23:12 diakopter have the nqpj emit a program of the mast serialized?
23:16 diakopter (I can see how to do it that way)
23:16 diakopter sorear: any ideas?
23:17 jnthn diakopter: oh...I meant it'd help us get NQP bootstrapped on Moar, not that it'd allow JVM -> Moar
23:17 jnthn We'll have to build something that dumps and then loads the thing up in Moar to do that...
23:17 diakopter can't use the existing serialized stuff in bytecode?
23:19 jnthn I'm not sure I follow?
23:19 diakopter put the entire tree as bytecode constants
23:30 diakopter no?
23:31 jnthn It sounds like a lot of throwaway work, is all.
23:32 diakopter jnthn: I guess I'm not seeing all the needed work
23:34 jnthn Well, it means writing some way to serialize the MAST tree in NQP, then deserialize it in Moar to then turn it into a bytecode file, iiuc?
23:34 sorear diakopter: I'm sorry, I wasn't paying any attention to the convo
23:34 diakopter jnthn: right
23:35 jnthn diakopter: That feels like a reasonable amount of work to me, is all :)
23:35 jnthn Maybe I'm just tired. ;-)
23:40 jnthn 'night
23:42 diakopter 'nite

| Channels | #moarvm index | Today | | Search | Google Search | Plain-Text | summary