From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: patching gcc to allow other calling conventions
Date: Sun, 17 Jun 2012 23:54:09 +0200 [thread overview]
Message-ID: <878vflzjsu.fsf@gnu.org> (raw)
In-Reply-To: CAGua6m0pvGLjHLfmoHCe_b5Qy4uKjewL9QPpOJVSVk5hSbHj8g@mail.gmail.com
Hi Stefan,
Stefan Israelsson Tampe <stefan.itampe@gmail.com> skribis:
> The reason I wanted to fork sbcl is that it has assemblers for
> x86,x86-64,alpha,hppa,sparc,ppc,mips e.g a few targets. It would be nice to
> know what targets to focus on or if we need to add anyone else to the list!
Did you consider starting from GNU/MIT Scheme? It supports only IA32
and x86_64, I think, but it’s in Scheme, and it’s GNU.
Thanks,
Ludo’.
next prev parent reply other threads:[~2012-06-17 21:54 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 [this message]
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
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=878vflzjsu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).