00:12 daxim joined 02:48 colomon joined 04:46 ggoebel111111110 joined 05:50 avuserow joined 06:13 garyaj joined 07:00 PerlJam joined, retupmoca joined, odc joined, leedo joined, nine_ joined 07:10 btyler_ joined 07:32 nine_ joined, leedo joined, retupmoca joined, btyler_ joined 07:37 PerlJam joined, odc joined, FROGGS joined 07:40 retupmoca joined, leedo joined, nine_ joined 08:33 zakharyas joined 09:06 kjs_ joined 09:48 brrt joined
brrt please somebody remind me to blog for moar one of these days (after the weekend) 09:49
09:53 avuserow joined, ggoebel111111110 joined, japhb joined, cxreg joined, lue joined 09:56 retupmoca joined, leedo joined, nine_ joined, cxreg joined 09:58 nebuchadnezzar joined, [Coke] joined 12:12 JimmyZ joined
JimmyZ masak: ping? 12:30
masak JimmyZ: pong 12:34
12:35 kjs_ joined
[Coke] seen in today's moar non-jit run: 13:49
S32-hash/delete-adverb.t...........................moar(34011,0x7fff7bce2310) malloc: *** error for object 0x7f8954e56840: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
sh: line 1: 34011 Abort trap: 6 nice -20 ./perl6-m t/spec/S32-hash/del
OSX.
Looks like that's the only fail on non-jit, but it cost 131 tests. 13:56
brrt [Coke] - are there jit-specific fails? 14:15
i kind of need to know about them :-)
also [Coke]++ for testing
timotimo brrt: how much have you looked at nativecall_invoke yet?
i'm asking just because i'd like to begin turning native call invocations into jitted stuff by using the jgb_append_call_c function 14:16
brrt i have not looked at it at all 14:17
timotimo OK
brrt where... is that stuff
:-)
timotimo so i'm not going to be trampling on previous work without knowing :)
brrt is that a new op?
timotimo nativecall.c is in core/ i think
brrt oh
i'll look
timotimo it's called nativecallinvoke actually 14:18
i think it'll be enough if i just look at it and ask specific questions directly, so you can focus on other stuff
[Coke] brrt: the JIT-specific failures are here when they are posted: 14:23
github.com/coke/perl6-roast-data/b...ummary.out
brrt thanks
timotimo: good idea :-)
[Coke] today? no failures on JIT. non-JIT is the problem. 14:24
brrt [Coke] - this is on which platform?
hmm
seems like flappiness
JIT is rather unlikely to do something right that was done wrong by the interpreter
[Coke] (but yesterday, S32-hash/delete-adverb.t had the failure non-jit had today; sounds like a flapper)
brrt yeah i agree
[Coke] brrt: right now is OS X. historically, it was linux.
timotimo brrt: have you considered building fast-paths for big integer arithmetic in the cases where both operands are stored as "small big ints"? 14:25
timotimo is AFK for a bit
brrt considered, yes, but i don't know if you can prove that they will always be fast paths
and you're going to end up testing-and-jumping for the case they are not
i can do that, and it will probably help a bit, but I don't know if the JIT is the right level for it 14:26
(of course the JIT should do it one day or another)
s/day/way/
I'm going to see if i can repeat those tests. we don't nearly have enough os-x based devs :-) 14:27
clang-is-so-damn-slow 14:30
14:32 lizmat joined
timotimo brrt: yeah, i expect that you'd have to test-and-branch 14:48
brrt hmmm 14:49
i'll be able to work on this in a week or so (hopefully)
timotimo neat (even though arguments would be more pressing or something like that) 14:50
brrt :-) 15:02
yeah i know i know
:-)
timotimo sorry for nagging you about that all the time :P
15:03 odc left
kjs_ re Mac OS devs: is there a ā€œpress this onceā€ button to run tests? Iā€™m happy to test now and again, but no time to develop 15:04
timotimo a simple script could be built using rakudobrew for building a fresh rakudo and then run the spec tests
brrt aye 15:05
rakudobrew would be a good place to put that
timotimo ah, yes
rakudobrew test moar
OSLT
brrt get to it 15:06
timotimo and then we could have a reporter
brrt or 'well volunteered'
:-)
i'm going to weekend
timotimo haha
have fun brrt
TimToady wonders if it would make more sense in some cases to just attempt the op and then branch on overflow, if it can be detected 15:25
timotimo we'd still have to check if the storage type is a "proper" bigint already or if it's a smallbigint 15:26
JimmyZ Isn't life simpler if there is Int class and BigInt Class :P 15:35
TimToady not for the user 15:37
JimmyZ aye
timotimo wouldn't it be easier to have a regular string that does the stringy stuff and a unicode string type that you use when you want to do unicody stuff? :P 15:38
timotimo AFK
TimToady in any case, the design of P6 assumes that people will write int64 or so when they want raw speed 15:39
JimmyZ agrees it 15:41
TimToady or have some pragma that says "use Int int64;"
JimmyZ constant Int = int64 :P
TimToady we'll need jnthn's N refactor first
"constant Int" will not necessarily switch the policy of using big integers for intermediate results 15:42
JimmyZ I saw constant utf8 = Blob[...] in the core setting 15:43
TimToady though I suppose we could say that if you redefined Int to be a native type, it magically assumes that you want that for intermediate results as well 15:44
but it might be wise to have a separate declaration for such semantic bending 15:45
then there's the folks who will want "constant Int = num" 15:46
JimmyZ yeah, I saw constant buf8 = Buf[uint8]; there
TimToady
.oO(constant Int = complex)
15:47
JimmyZ :P
TimToady some people may actually think they want constant Num = Complex 15:49
though it's probably sufficient to redefine sqrt to always return complex 15:50
[Coke] we need something like smolder to record test runs.
[Coke] is reminded to get back to trying to get spectest runs into jenkins. 15:51
JimmyZ Good night ... 15:53
15:54 lue joined 16:04 Guest1419 joined 16:26 FROGGS joined 16:55 colomon joined 17:36 kjs_ joined 17:51 FROGGS joined 21:26 woolfy1 joined 21:27 lizmat_ joined 22:43 japhb joined, avuserow joined
dalek arVM/closefhi: 8d9f84a | (Tobias Leich)++ | / (14 files):
implement nqp::closefhi which retuns the exit code of a pipe

nqp::openpipe returns a file handle one can read from, but since such an opened pipe is actually a spawned process we also need its exit code to know if it run cleanly. Use nqp::closefhi on such a file handle if you are interested in the exit code, nqp::closefh if you are not.
22:46
22:48 ggoebel111111110 joined