On Wed, 2013-05-22 at 00:23 -0400, Noah Lavine wrote:
> On Sun, May 19, 2013 at 6:02 PM, Ludovic Courtès wrote:
>
> > Andy Wingo skribis:
> >
> > > On Sat 18 May 2013 15:44, Noah Lavine writes:
> > >
> > >> I have a very small question, based on something I think you said
> > >> earlier - since
On Sun, May 19, 2013 at 6:02 PM, Ludovic Courtès wrote:
> Andy Wingo skribis:
>
> > On Sat 18 May 2013 15:44, Noah Lavine writes:
> >
> >> I have a very small question, based on something I think you said
> >> earlier - since the container will be ELF, will we call our files .so
> >> now?
> >
>
Hi,
On Mon 20 May 2013 00:06, l...@gnu.org (Ludovic Courtès) writes:
>> Once the RTL branch is all merged in, we can start doing the same with
>> Noah's wip-rtl-cps branch.
>
> I’m unclear on what the safest or easiest approach is. My natural
> tendency would have led me to start by “just” rewri
Hello!
This is all very exciting!
Andy Wingo skribis:
> However, I think we've done all we can in branches. I think we should
> bless this RTL experiment as the way to do Guile 2.2. (Thoughts or
> objections welcome.) To that end, I think we need to start merging
> wip-rtl into master.
>
> W
Andy Wingo skribis:
> On Sat 18 May 2013 15:44, Noah Lavine writes:
>
>> I have a very small question, based on something I think you said
>> earlier - since the container will be ELF, will we call our files .so
>> now?
>
> We certainly can. Is it a good idea though?
I’d vote for keeping .go,
Hi :)
On Sat 18 May 2013 15:44, Noah Lavine writes:
> I have a very small question, based on something I think you said
> earlier - since the container will be ELF, will we call our files .so
> now?
We certainly can. Is it a good idea though? It might conflict with .so
Makefile rules in some
This is very exciting! I have a very small question, based on something I
think you said earlier - since the container will be ELF, will we call our
files .so now?
Noah
On Fri, May 17, 2013 at 5:49 PM, Andy Wingo wrote:
> Friends! Schemers! Gentle Guilefolk! The time has come to begin in
>
Hi,
On Sat 18 May 2013 07:00, Nala Ginrut writes:
> I saw that our current ELF just wraps the .go code, not the native code.
This is imprecise. Think of ".go" and "ELF" as containers for code and
data. It doesn't make sense to wrap a container in a container :)
Currently in stable-2.0, the c
Nice guys~ very impressive work!
I saw that our current ELF just wraps the .go code, not the native code.
Maybe it's possible to try a naive AOT compiler now. IMO, translate RTL
bytecode to native asm code, say, i386 assemble code. Then call gas to
assemble it.
I do know Andy's expectation is to w
