Re: Mes 0.10 released

2017-09-11 Thread Jan Nieuwenhuizen
Arne Babenhauserheide writes: > Jan Nieuwenhuizen writes: >> Arne Babenhauserheide writes: >>> Jan Nieuwenhuizen writes: I am pleased to announce the release of Mes 0.10, representing 82 commits over 6 weeks. Mescc now compiles a bootstrappable-modified TinyCC into a mes-tcc that

Re: Mes 0.10 released

2017-09-11 Thread Arne Babenhauserheide
Jan Nieuwenhuizen writes: > Arne Babenhauserheide writes: >> Jan Nieuwenhuizen writes: >>> I am pleased to announce the release of Mes 0.10, representing 82 >>> commits over 6 weeks. Mescc now compiles a bootstrappable-modified >>> TinyCC into a mes-tcc that in turn can successfully compile a t

Guile in the browser [Was: Summer of Code Recap]

2017-09-11 Thread Amirouche Boubekki
Héllo all, As you may know ijp was working during GSoC on a JavaScript backend for Guile. What it means is that now, thanks to his brillant work one can translate pure Guile to JavaScript and run it in a browser supporting Tail Call Optimization (TCO). After a looking up the web for ways to run

Re: out-of-control GC

2017-09-11 Thread Hans Åberg
> On 9 Sep 2017, at 21:47, Linas Vepstas wrote: > > I've been experiencing problems with guile GC for a while now, that I've > mostly been able to ignore, but that are becoming debilitating, and I need > help, or need to find some solution. > > Background: I have a C++ library that has guile bi

Re: Mes 0.10 released

2017-09-11 Thread Jan Nieuwenhuizen
Arne Babenhauserheide writes: > Jan Nieuwenhuizen writes: > >> I am pleased to announce the release of Mes 0.10, representing 82 >> commits over 6 weeks. Mescc now compiles a bootstrappable-modified >> TinyCC into a mes-tcc that in turn can successfully compile a trivial >> C program. > > Nice!

Re: Mes 0.10 released

2017-09-11 Thread Arne Babenhauserheide
Jan Nieuwenhuizen writes: > I am pleased to announce the release of Mes 0.10, representing 82 > commits over 6 weeks. Mescc now compiles a bootstrappable-modified > TinyCC into a mes-tcc that in turn can successfully compile a trivial > C program. Nice! How big are your changes to TinyCC? Bes

Re: out-of-control GC

2017-09-11 Thread Arne Babenhauserheide
Marko Rauhamaa writes: > I have no idea how good Guile's performance is. Python's performance is > probably about 100 times worse than C, yet it's the fast becoming the > most popular programming language in the world. One of the reasons for that is that you can get it to native C for most non-t

Re: out-of-control GC

2017-09-11 Thread Kjetil Matheussen
> linasveps...@gmail.com: > > I've been experiencing problems with guile GC for a while now, that I've > mostly been able to ignore, but that are becoming debilitating, and I need > help, or need to find some solution. > > Background: I have a C++ library that has guile bindings; it is wrapped up

Re: Guile bugs

2017-09-11 Thread Ludovic Courtès
Hi Marko, Marko Rauhamaa skribis: > l...@gnu.org (Ludovic Courtès): > >> I don’t know to what extent that is applicable to your software, but my >> recommendation would be to treat that network socket as a Scheme port, >> pass it to ‘read’, and pass the result to ‘eval’ (as opposed to reading >>

Re: out-of-control GC

2017-09-11 Thread tomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Sep 10, 2017 at 04:47:09PM -0500, Linas Vepstas wrote: [...] > The bigger the RAM usage, the slower it seems to be. It might be due to > fragmentation [...] Your guesses all make much sense (gc and non-gc data mixed at page level, forcing t

Re: Guile bugs

2017-09-11 Thread Marko Rauhamaa
l...@gnu.org (Ludovic Courtès): > I don’t know to what extent that is applicable to your software, but my > recommendation would be to treat that network socket as a Scheme port, > pass it to ‘read’, and pass the result to ‘eval’ (as opposed to reading > the whole string from C++ and passing it to

Re: Guile bugs

2017-09-11 Thread Ludovic Courtès
Hello, Linas Vepstas skribis: > The stuff coming over the network sockets are bytes, not s-exps. Since none > of the bytes are ever zero, they are effectively C/C++ strings, and are > handled as such. These C strings are sent to scm_eval_string() wrapped > by scm_c_catch(). I don’t know to wha