github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm
Set by AlexDaniel on 12 June 2018.
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
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
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
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
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
timotimo we've implemented it ourselves i think 16:46
but it's really just realloc + memset
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
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
MasterDuke timotimo: do you see anything i'm doing wrong? github.com/MasterDuke17/libtommath...79f80fdf01 18:51

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!