unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: Daniel Krueger <keenbug@googlemail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: patching gcc to allow other calling conventions
Date: Thu, 21 Jun 2012 20:53:57 +0200	[thread overview]
Message-ID: <CAGua6m3q2ZEWUw0zxT8YivzzmeW1Z84n0xtnPjeY74W2R93FaQ@mail.gmail.com> (raw)
In-Reply-To: <CAAh5vOP+yK2grEokYi=YqfXeMZLOq=8RGbzF4zghQ7sCKrNprA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

Hmm, yes then it can work.

I would compile only to C at the first phase as you say as it should not be
of too high
complexity to output the C part and be pretty swift although you are
interpreting. Then the VM can compile all guile including code to emit and
compile assembler and then one can add the possibility to compile to native
code by some kind of just in time mechanism. Cool!

I will try to start investigating this approach.

/Stefan

On Thu, Jun 21, 2012 at 7:57 PM, Daniel Krueger <keenbug@googlemail.com>wrote:

> On Thu, Jun 21, 2012 at 7:50 PM, Stefan Israelsson Tampe
> <stefan.itampe@gmail.com> wrote:
> > On a second thought guile do have an initital interpreter that is either
> a
> > vm or a native no?
> > Perhaps one can make use of that somehow!
>
> Yeah, I thought about that too, but thought first that it would be
> impossible. But if you first only compile the interpreter code
> (without the VM), then create the C file with the instructions and
> compile the VM it should work. I think .. ^^
>
> - Daniel
>

[-- Attachment #2: Type: text/html, Size: 1487 bytes --]

  reply	other threads:[~2012-06-21 18:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15 18:47 patching gcc to allow other calling conventions Stefan Israelsson Tampe
2012-06-17 21:54 ` Ludovic Courtès
2012-06-18  0:43   ` Noah Lavine
2012-06-18 16:59     ` Stefan Israelsson Tampe
2012-06-18 22:30       ` Noah Lavine
2012-06-18 22:55         ` Ludovic Courtès
2012-06-21 12:32         ` Stefan Israelsson Tampe
2012-06-21 17:14           ` Daniel Krueger
2012-06-21 17:50             ` Stefan Israelsson Tampe
2012-06-21 17:57               ` Daniel Krueger
2012-06-21 18:53                 ` Stefan Israelsson Tampe [this message]
2012-06-21 21:01             ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGua6m3q2ZEWUw0zxT8YivzzmeW1Z84n0xtnPjeY74W2R93FaQ@mail.gmail.com \
    --to=stefan.itampe@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=keenbug@googlemail.com \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).