github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm
Set by AlexDaniel on 12 June 2018.
timotimo aras-p.info/blog/2019/09/28/Clang-...-Analyzer/ 02:34
^- moarvm build times are already relatively good, but maybe there's something glaringly obvious we can improve 02:35
nine timotimo: I'd love for our install phase to be more parallelization friendly 06:35
nwc10 good *, #moarvm 07:16
MasterDuke nine: yeah, especially with everybody having ssds, all those cps can probably be parallelized for a significant speedup. do the various chunks in there need to be split into sub-tasks and then 'install' depend on them? 07:42
Geth MoarVM: taboege++ created pull request #1353:
Use GMP instead of libtommath		 08:58
timotimo nine: sae 09:08
same*
timotimo i wonder how much faster it would be if we could use cp instead of perl ExtUtils::Command 10:59
oh wow 11:11
yeah that's ... very fast actually 11:12
MasterDuke istr some change in the repos about this. maybe consolidating all on ExtUtils::Command? 11:49
a year or so ago
MasterDuke one used to have a check if it was linux and used cp instead, but i think that was removed? 11:51
Geth MoarVM/new-disp: 0d2933a205 | (Jonathan Worthington)++ | 2 files
Provide a way to walk dispatchers on the callstack
 12:06
MoarVM/new-disp: bab515adee | (Jonathan Worthington)++ | 3 files
Rename dispatcher-[set|get]-state

The initial design idea conflated two things that seem better off being separated:
  * The (immutable) set of arguments for initializing a resumption - which
   is what this call will now we used for.
  * The (mutable) state that can be saved in the dispatch and changes as
   we walk through candidates (which will get a new field in the root
   dispatcher frame)
Geth MoarVM/new-disp: f7719162b1 | (Jonathan Worthington)++ | 3 files
Internals renamings regarding state -> resume init
 12:19
brrt \o 12:53
re: JJMerello's request, do we have anything for hacktoberfest?
jnthn Hm, probably not at the moment...what's does it need exactly? 13:04
Approachable issues? 13:05
nwc10 o/ 13:11
brrt yes, something approachable 13:33
preferably something that people can do easily as an introduction
jnthn Of all things I expected might bite the current approach, continuations were one I missed... 14:01
(Wanted callstack records of a resumption to point back to the dispatch they are a resumption of. But if you manage to wedge a continuation reset between the two points, it can become dangling.) 14:03
Geth MoarVM/new-disp: 90033cddc9 | (Jonathan Worthington)++ | 3 files
Stub in boot-resume[-caller]
 14:57
MoarVM/new-disp: a06c9d737a | (Jonathan Worthington)++ | 3 files
Wire up boot-resume[-caller] to a record function
MoarVM/new-disp: 12e04df951 | (Jonathan Worthington)++ | 3 files
Start persisting resumption points

So that they can be identified in the dispatch program. For now, just the dispatcher name, however the resume initialization state shall be added later on.
jnthn language class time; bbl 15:16
timotimo so walking the stack for dispatchers is the solution for "nextsame" and friends being monomorphic? 15:17
MasterDuke tobs: i can repro the failure seen in azure after your last commit. `Generating src/gen/config.c ............................ FAIL unknown configuration key 'gmpconf'` 19:19
tobs MasterDuke: makes sense, as I didn't know where else new config keys have to be announced. (I thought I finished a test build though... anyway, will fix soon.) 19:44
tellable6 tobs, I'll pass your message to MasterDuke
MasterDuke tobs: i just tried adding gmp.h to src/6model/reprs/P6bigint.h and then adding some calls to gmp functions in src/math/bigintops.c, but i get the error ``/usr/bin/ld: 3rdparty/gmp/libgmp.a(bdiv_q_1.o): warning: relocation against `__gmp_binvert_limb_table' in read-only section `.text'/usr/bin/ld: 3rdparty/gmp/libgmp.a(bdiv_q_1.o): relocation 21:12
R_X86_64_PC32 against symbol `__gmp_binvert_limb_table' can not be used when making a shared object; recompile with -fPIC/usr/bin/ld: final link failed: bad value
tellable6 2020-09-24T19:44:33Z #moarvm <tobs> MasterDuke: makes sense, as I didn't know where else new config keys have to be announced. (I thought I finished a test build though... anyway, will fix soon.)
tobs MasterDuke: I'm on it (today with my laptop plugged in). Let's see if -fPIC is actually set. 21:14
MasterDuke it is
some random SO answer suggested moving -lgmp last, but that didn't change anything 21:15
tobs I hope it is okay that I forced-pushed an update to that branch for the src/gen/config.c error, MasterDuke 21:27
MasterDuke np, no error now 21:30
(other than the new relocation one)
tobs unrelated to that error, but I think that currently gmp is configured too late. Invoking the configure script is what generates gmp.h from gmp.h.in, so that header would not be available to moarvm files compiled before gmp is configured (which happens as part of the build rule right now). Is there already a way to configure a 3rdparty dependency as part of executing Configure.pl? 21:51
unfortunately, it's bed time here already. I suppose it will be easier to link to a shared library GMP after all, configured to install into some moar-specific $PREFIX because of issue #321. 22:11
MasterDuke i'm too bed to 22:15
moon-child any thought given to adding a disassembly primitive, like lisp has? 22:31

Powered by Cro and the Raku® Programming Language.

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

Thank you!