<stikonas>vagrantc: tar should be simple enough to implement in M2-Planet's C subset <stikonas>vagrantc: although we do have an issue where wrong file is extracted <stikonas>but in any case, correctly parsing tar sounds easier than e.g. writing M2-Planet <stikonas>vagrantc: but I did observe some minor non-critical issues in live-bootstrap when we tried to extract tarballs <stikonas>usually some extra empty file appears alongside source ***ChanServ sets mode: +o janneke
<oriansj>stikonas: about the M0 segment fault; there are quite a few ways to segfault M0 such as just doing DEFINE foo and then just end the file <oriansj>it isn't supposed to be robust but as guick and ugly of a hack in as little hex2 as you can get away with. <oriansj>as for the get_machine segfault, yes that is fixed in the latest mescc-tools <oriansj>I mean if you want to make RISC-V's M0 being the best M0 around: go for it <oriansj>and if there are issues with the tar files and the mescc-tools-extra untar program, I probably should fix those <stikonas[m]>Hmm, I probably wouldn't bother... Trying to work on m2-planet macros <oriansj>hint line feed is preserved for use by the macro processor and stripped before being passed to cc_core.c <oriansj>and -E option will show you what the macro expansion is ***stikonas_ is now known as stikonas
***stikonas_ is now known as stikonas