01:26
BenGoldberg joined
01:48
woolfy joined
02:16
woolfy joined
02:17
rurban1 joined
02:20
BenGoldberg joined
03:17
Ben_Goldberg joined
03:40
ggoebel18 joined
03:47
ggoebel19 joined
06:18
rurban1 joined
06:21
sorear joined
|
|||
nwc10 | jnthn: I left valgrind running, and it finds no problems | 08:45 | |
FROGGS[mobile] | not too bad | 08:54 | |
09:39
rurban1 joined
10:32
lizmat_ joined
12:16
tgt joined
|
|||
jnthn | nwc10: Nice | 12:20 | |
nwc10 | jnthn: you are having the appropriate amount of fun? | 12:49 | |
jnthn | nwc10: I'm...uh..packing clothes for a week's trip away | 12:50 | |
nwc10 | where you are going, is the beer good? | ||
jnthn | Stockholm | 12:52 | |
Yes :) | |||
Confirm that I make it to stage optimize here as well | 16:01 | ||
FROGGS | I'd like to know why I die that early with an optimized moar | 16:02 | |
I mean, I can build nqp just fine, and it dies when compiling Perl6::BOOTSTRAP | 16:03 | ||
jnthn | Oh...I have an optimized one here and make it all the way through the optimize stage | ||
FROGGS | "Heap corruption detected: pointer 0x65b5178 to past fromspace" | ||
jnthn | *to the | ||
FROGGS | ohh | ||
the bt only shows MVM_args_slurpy_positional as an interesting step | 16:04 | ||
jnthn: how long does stage parse take then? | 16:05 | ||
and what is your vm/parrot's stage parse? | |||
jnthn | Forever.... I don't know about the latter number. I know it's a bunch slower than JVM. | 16:07 | |
FROGGS | I believe it took 460s on my box (unoptimized) | 16:08 | |
16:26
cognominal joined
|
|||
jnthn | I'm working on getting rid of the massive warnings spewing... | 16:27 | |
FROGGS | uhh, nice :o) | 16:31 | |
diakopter is curious how long moar takes to parse the setting compared to jvm | 16:32 | ||
FROGGS | ohh | 16:39 | |
the gc debug output takes 2.5GB >.< | |||
timotimo | sounds good :D | ||
oh wow, that's a bunch | |||
FROGGS | good that I have an SSD :o) | ||
timotimo | does it dump out the whole nurseries? :P | 16:40 | |
diakopter | essentially... | ||
timotimo | er, we do have nurseries, right? | ||
diakopter | in the gcorch branch the debug output is much more granular | 16:41 | |
(controlled) | |||
FROGGS | hmmm, the address from the error message is not in that output :/ | ||
diakopter | search case-insensitive? | 16:42 | |
17:04
rurban1 joined
|
|||
rurban1 | diakopter: urcu is also bsd, cygwin and more. Until recently RCU was patent encumbered, not anymore. LGPL is a problem? You can simply link to it, no problem. Only inlining large parts would be. | 17:05 | |
nwc10 | jnthn: I get: | 17:06 | |
Stage start : 0.000Nominal type check failed for parameter '%spec'; expected Associative but got BOOTHash | |||
oh, well, sort of like that. Clearly the terminal had the munchies | 17:07 | ||
FROGGS[mobile] | nwc10: I believe you are missing a commit | 17:08 | |
nwc10 | but no 10 PRINT "NYI"; 20 GOTO 10 | ||
FROGGS[mobile]: Rakudo is at a6eeb0b159b82f41a2088cb20105f651fdead89b | |||
Implement nominal type checks in binder | |||
everything seems to be current | 17:09 | ||
FROGGS[mobile] | then it might be right, cant check right now | ||
right, the BOOTHash msg from sat/fri was a different one | 17:11 | ||
jnthn | nwc10: Yup, me too | 17:14 | |
nwc10: I implemented the missing type check and it caught something we got away with before | 17:15 | ||
oh, joy...the train now as a "technical problem"... | 17:22 | ||
timotimo | more time to hack before you arrive ;) | 17:23 | |
nwc10 | jnthn: the "technical problem" affects movement? Or screws the lights, the food and the Internet too? | 17:45 | |
is the gravity on the blink yet? | |||
timotimo | don't blink | ||
don't even blink | |||
blink and you're dead | |||
jnthn | nwc10: Movement, for a while. We're going againnow.... | 17:50 | |
dalek | arVM: 50a6529 | jonathan++ | src/core/interp.c: Bring iscont inline with other backends. |
17:51 | |
FROGGS | diakopter: no, it already was a case-insensitive search | 17:52 | |
jnthn | detrain & | 17:55 | |
18:31
colomon joined
20:20
jnap joined
|
|||
jnthn | OK, got local commits that recover us to the point we were at before, but with the sig binder actually enforcing type checks... | 21:43 | |
FROGGS | jnthn++ # :o) | 21:45 | |
jnthn | I've also got a lead on what's making setting compilation so utterly slow. | ||
FROGGS | ohh cool! | ||
that is way more interesting :D | |||
do tell | |||
jnthn | (mind-blowing number of call frames hanging around | ||
FROGGS | ohh | 21:46 | |
jnthn | And I can guess where from, *and* I think if we can fix it we might well get a win on all backends. | ||
diakopter | why's that | ||
FROGGS | could that case the "Heap corruption detected: pointer 0x65b5178 to past fromspace"? | ||
jnthn | No, that sounds like a plain old bug... | ||
tadzik | how boaring | 21:47 | |
FROGGS | awesome | ||
diakopter | roar | ||
FROGGS | gah | ||
how goating | |||
diakopter | boaning | ||
jnthn | I love how talking about goating makes diakopter thing about boaning :P | 21:48 | |
*think | |||
diakopter | gloating | 21:49 | |
FROGGS | now you're just woaffling :P | 21:50 | |
diakopter | jnthn: lemme guess: past stub clones | 21:52 | |
jnthn | no, something grammar related | ||
diakopter | I thiught that was grammar related | 21:53 | |
FROGGS | thought* # that was grammar related | ||
sort of | |||
diakopter | hee | 21:54 | |
FROGGS | damn it... how should I sleep now when there might be a win on all backends out there?? | ||
tadzik | don't sleep, let's not sleep together | 21:55 | |
...that sounds a bit bad | |||
dalek | arVM: 4867b27 | jonathan++ | src/core/hll. (2 files): Support HLL array/hash/code mappings. |
||
FROGGS | been there, done that :o) | ||
diakopter | tadzik: but, ćcryć | 21:57 | |
well that didn't work out very well | 21:59 | ||
(now on a real keyboard) | |||
22:12
cognominal joined
|
|||
jnthn | OK, my prototype of the change makes CORE.setting compilation time on Moar about 2/3 of what it was before...and seems to shave some space off | 22:35 | |
I'm going to push it to a branch in NQP and leave testing on other platforms to @other | 22:36 | ||
timotimo | yays! | ||
jnthn | Also it warrants a Rakudo spectest run on it too | ||
FROGGS | I'll do that and report after $sleep | 22:37 | |
benabik | What change makes CORE take 2/3rds the time? | 22:42 | |
timotimo | github.com/perl6/nqp/commit/3b280649c2 | ||
jnthn | benabik: Only tried on Moar, and only stage parse. | ||
diakopter | jnthn: so what's keeping that cursor hanging around | 22:43 | |
jnthn | diakopter: Well, cursors stay around because match objects point to them. | 22:44 | |
diakopter: But there's no reason cursors we'll never backtrack into need to keep pointing at other things. | |||
diakopter | even failed cursors? | ||
er, failed matches | |||
jnthn | Yeah, but those tend not to stick around long anyway | 22:45 | |
Especially as <foo>? is now Nil | |||
There's something that makes me uneasy though...the fix I did shouldn't have helped as much as it did, or so goes my gut feeling | 22:46 | ||
diakopter | right, that's my gut feeling too | ||
which I was trying to express by those questions :) | |||
jnthn | Or at least, if may help other backends proportionally do how it helped Moar. | 22:47 | |
Which is *fine*. :) | |||
But still leaves us with some stuff to hunt down :) | |||
diakopter | it hints that there are plenty larger gains out there | ||
jnthn | Aye. | ||
diakopter | "they're not inefficiencies! they're potential programmer rewards!" | 22:48 | |
jnthn | Well, one advantage I have with Moar is I understand it near enough fully and can do quick instrumentation hacks if I need to go exploring... | ||
Ah...yeah, something needs looking into | 22:49 | ||
The inter-generational roots list is huge. | 22:50 | ||
diakopter | oo that's a potential big gain :) | 22:51 | |
jnthn | Well, I once knew we had algorithmic todo there, but I did that a while back. But yeah, that shouldn't happen. Will need to work out why. | ||
timotimo | jnthn: see #perl6, on parrot i get no big speed improvement | ||
like 4% perhaps | 22:52 | ||
jnthn | timotimo: OK. What about memory, ooc? | 22:53 | |
timotimo | i'll have to measure that more carefully | ||
i'm doing the spectests ATM | |||
should i measure the memory usage first? | |||
jnthn | Well, whatever order you wish :) | 22:56 | |
Something odd is that we seem to box an insane number of ints | |||
FROGGS | moar stage parse is 318.597s, was 468s | 22:57 | |
diakopter | win. | 22:58 | |
jnthn | Nice | ||
Well, "nice" | |||
FROGGS | :o) | ||
diakopter | that's still about 318 more seconds than I'd hope it to be eventually | ||
timotimo | oh wow. | ||
you have some high ambitions | |||
FROGGS | diakopter: that is an unoptimized moar | ||
diakopter | timotimo: like you wouldn't even believe | 22:59 | |
FROGGS | it only takes a few seconds (to explode) using an optimized moar though | 23:00 | |
timotimo | oh yikes | ||
benabik | Erm. Exploding bad. | ||
timotimo | so the parrot spectests are completely clean except the one failure froggs also has had for ages | 23:01 | |
FROGGS | benabik: but it explodes fast :o) | ||
and that is what we want after all | |||
benabik | Slow explosions are just burning. ;-) | ||
jnthn | OK, sleep time for me :) | 23:02 | |
'night | |||
FROGGS | gnight jnthn | 23:03 | |
diakopter | FROGGS: wait, asplode? | 23:04 | |
FROGGS | diakopter: yes | ||
diakopter | boo | ||
FROGGS | a gc bug as it seems | 23:05 | |
missing MVMROOT probably | |||
diakopter | I'm curious if the gcorch branch fixes it (once the gcorch branch is fixed to work at all really) | ||
timotimo | yeah, when is that going to hit master? :) | 23:08 | |
benabik | Presumably sometime after it starts working. | ||
diakopter | <shrug> | ||
timotimo | i guess that's fair | ||
diakopter | I'll have to kickban dalek temporarily so jnthn doesn't notice the merge ;) | 23:09 | |
that was a joke, future jnthn | 23:13 | ||
timotimo | i wonder what big problems moarvm has for parsing performance | 23:16 | |
FROGGS | I'll compile tomorrow on windows to see how fast/slow an optimized moar does it | 23:21 | |
timotimo | should i do JVM today? | 23:23 | |
FROGGS | I did, 54s, but I dunno how long it took before | 23:24 | |
currently spectesting both | |||
no difference in p's stage parse, as you mentioned | 23:26 | ||
gnight | 23:28 | ||
timotimo | ginte :) | ||
23:50
BenGoldberg joined
23:56
FROGGS joined
|