github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm
Set by AlexDaniel on 12 June 2018.
00:00 reportable6 left 00:04 reportable6 joined 00:44 zakharyas joined 01:21 lucasb left 01:24 AlexDani` joined 01:27 AlexDaniel left 01:28 AlexDani` is now known as AlexDaniel, AlexDaniel left, AlexDaniel joined 03:23 pamplemousse joined 04:00 pamplemousse left 04:49 squashable6 left 04:52 squashable6 joined 06:00 reportable6 left 06:01 reportable6 joined 06:11 brrt joined
brrt \o 06:26
nwc10 o/ 06:29
ASAN finds your new code very boring. 06:30
brrt blegh 06:32
what's writing in C like if we don't get a few SEGVs along the way 06:33
06:33 sena_kun joined 06:35 sena_kun left 07:47 brrt left
Geth MoarVM/expr-jit-devirtualize: 1c41e276f3 | (Bart Wiegmans)++ | src/jit/expr.c
[JIT] Get type object for type-variant opcodes

Stolen from the devirtualization code in graph.c
07:50
08:56 squashable6 left 08:58 squashable6 joined 09:11 squashable6 left 09:14 squashable6 joined, sena_kun joined 09:16 domidumont joined 09:36 domidumont left 09:39 zakharyas left 09:48 MasterDuke left 11:19 pamplemousse joined, pamplemousse_ joined 11:20 pamplemousse_ left 12:00 reportable6 left, reportable6 joined 12:38 brrt joined
brrt \o 12:38
pamplemousse o/
brrt ohai pamplemousse
I saw your summary post. Well done 12:39
pamplemousse Thanks! Is there anything you think I should add, or clarify?
brrt Not really... btw, I think using tar to pack a directory into a file has excellent precedence 12:41
we/you/someone should post them on reddit 12:42
pamplemousse Good to know! I thought it was way cleaner than what I was originally trying to do. 12:43
I'll post it! Just wanted to get another set of eyes on it so I could check that I hadn't missed anything big. 12:44
For anyone interested here, my summer in review post is up: yakshavingcream.blogspot.com/2019/...eview.html 12:51
13:18 lucasb joined 14:04 domidumont joined 14:11 pamplemousse left 14:37 hoelzro left 14:38 hoelzro joined 15:13 brrt left 15:36 brrt joined 15:40 MasterDuke joined
MasterDuke jnthn: my question was pretty bad. what i want to do is not require the user to calloc the memory. i guess i could memset it to zero? i guess i don't understand why the realloc causes that particular error 15:51
15:59 brrt left 16:13 domidumont left 16:17 brrt joined 16:19 tellable6 left 16:20 tellable6 joined
timotimo when you calloc, you should also use recalloc instead of realloc so the new data gets zeroed out, too 16:25
MasterDuke timotimo: is recalloc available everywhere? 16:26
16:37 AlexDaniel is now known as jntn, jntn is now known as jnth, jnth is now known as AlexDaniel
timotimo we've implemented it ourselves i think 16:46
but it's really just realloc + memset
16:50 reportable6 left, nativecallable6 left 16:51 reportable6 joined 16:55 brrt left, nativecallable6 joined, brrt joined
MasterDuke that won't help me though. the error/warning is happening during the realloc. so i'll still get it even if i memset after 16:57
17:01 brrt left 17:14 sena_kun left 17:32 pamplemousse joined
timotimo in that case it sounds like the pointer itself isn't quite right 18:02
i.e. you could be passing an uninitialised address to realloc
i mean not what it points to, the pointer itself 18:03
18:40 sena_kun joined 18:41 sena_kun left 18:50 robertle joined
MasterDuke timotimo: do you see anything i'm doing wrong? github.com/MasterDuke17/libtommath...79f80fdf01 18:51
19:00 pamplemousse left 19:15 AlexDaniel is now known as mom 19:16 mom is now known as yourmom, yourmom is now known as I` 19:17 I` is now known as someone`, someone` is now known as also 19:18 also is now known as such, such is now known as or, or is now known as and, and is now known as can` 19:19 can` is now known as when, when is now known as you` 19:20 you` is now known as think 19:21 think is now known as AlexDaniel, AlexDaniel is now known as could, could is now known as why` 19:22 why` is now known as AlexDaniel 19:57 brrt joined 20:19 brrt left 21:13 pamplemousse joined 21:29 brrt joined 21:41 brrt left 22:07 lizmat left