IRC channel logs

<fossy>pabs3: reintroducing go, which should be easy, then all of the other guix ones

<OriansJ>siraben: merged. Thank you

<OriansJ>fossy: 16bit mode in M1; just requires 16bit defines and can be freely combined.

<roptat>if anyone is intereste in doing a PhD thesis on bootstrapping (mostly Java stuff I think, but not necessarily): https://softwarediversity.eu/hardening-the-software-supply-chain-with-multi-compilers/

<roptat>(well to be fair, not *only* bootstrapping, but that's a big part of it, and it's all motivated by the trusting trust talk :))

<lfam>Very cool opportunity

<fossy>I would totally do that if I was in such a stage of education to do so

<jelle>that's amazing!

<civodul>roptat: nice!

<civodul>are they former colleagues of yours?

<roptat>not at all, though they used to work at Inria, in Rennes ^^

<roptat>do you think it'd make sense to share the link on guix-devel maybe?

<civodul>yes, sure

<civodul>and on the "bootstrappable" mailing list

<janneke>roptat: oh, very nice

<roptat>sent :)

<pder>OriansJ: I pushed some more changes to blynn-compiler. I followed the pattern of what you did with vm.c to rts.c. I reformatted with astyle and changed enums to CONSTANTS etc

<pder>I think to get around the limitation in M2-Planet with unsigned prog[] = {1,2,3,4...} I should be able to just define a string char * prog = "1,2,3,4"

<pder>There is already loadRaw() in vm.c that can parse this string and populate the mem array

<yt>OriansJ: finally got approval from work to contribute to mescc-tools and mescc-tools-seed! I'll do some cleanup tomorrow and get those pull requests of the aarch64 port up

<yt>Janneke: while I was waiting for that I had some fun with mes and mescc. aarch64 port for mes is done and mescc is in the works. will need to get separate approval for that though, so pull requests will have to wait a bit again :(

<xentrac>congratulations yt!

<janneke>yt: beautiful!

<xentrac>that will be great!

<vagrantc>yt: eagrely away the aarch64 port! :)

<vagrantc>awaity

*vagrantc stares at keyboard

<OriansJ>pder: very nice; I just did some refinements to vm.c

<OriansJ>yt: excellent; we look forward to reviewing your work ^_^

<OriansJ>pder: you'll notice that vm.c and rts.c are now alot more simiiar. So we might be able to eliminate the compiling steps using rts.c with some cleverness in vm.c

<yt>Oriansj: first pull request is up: https://github.com/oriansj/mescc-tools/pull/11

<yt>That's probably the smallest change I'll do XD

<OriansJ>I'll begin reviewing immediately

<yt>for the big changes on mescc-tools-seed, do you mind if I leave the (messy) git history in the pull request and we can squash it in the merge?

<OriansJ>it is merged yt; thank you for the improvement

<yt>awesome, that's my prerequisite in then :)

<OriansJ>yt: how you wish to contribute your work is up to you; just understand bigger changes take longer to review

<yt>that's fair enough. I suppose I could do each tool separately

<pder>excellent Oriansj, I pushed another change in which the hs files generate a char * for prog, and rts_init parses it

<OriansJ>pder: nice let us see if we can have the hs files dump to generated/ their blob and then if vm -lf or -lfr will work well enough

<OriansJ>so please checkout out my latest commit pder

<OriansJ>*be back in a bit*

<yt>OriansJ: what is the appropriate GNU header for the files in mescc-tools-seed? for example, the files in the AMD64 port identify themselves as any of Mes, mescc-tools, M2-Planet, or stage0 :D

<yt>as part of any of*

<OriansJ>yt: stage0 will be fine

<yt>I'll stick with that, thanks!

<pder>fetched it and merged it locally. Looks great and everything built ok with gcc

IRC channel logs

2020-12-03.log