From: Noah Lavine <noah.b.lavine@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel@gnu.org
Subject: Re: Hi! Interested in GSoC. Feedback on these ideas?
Date: Thu, 7 Apr 2011 09:10:26 -0400 [thread overview]
Message-ID: <BANLkTimX0+-0uVf-LJxi9_0fX7EMXLthWQ@mail.gmail.com> (raw)
In-Reply-To: <871v1ecvjr.fsf@netris.org>
Hello,
> There is one _very_ serious problem with using GCC to compile Scheme, or
> at least there was the last time I researched this issue: tail calls.
I might be wrong about this, but I thought that GCC supported multiple
calling conventions, with the user telling GCC which one to use
(cdecl, fastcall, possibly others). If so, it must have some way to
represent that in its intermediate representations. We might be able
to add our own calling convention.
I also know that GCC has an --optimize-sibling-calls argument, which
will make it do something similar to at least some regular C calls.
I'm not sure if it's possible, but maybe we could arrange for whatever
code transformation implements this to be run on every Scheme call.
Noah
next prev parent reply other threads:[~2011-04-07 13:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 0:40 Hi! Interested in GSoC. Feedback on these ideas? Paul Raccuglia
2011-04-07 3:36 ` nalaginrut
2011-04-07 8:31 ` Mark H Weaver
2011-04-07 13:10 ` Noah Lavine [this message]
2011-04-07 14:12 ` nalaginrut
2011-04-07 14:25 ` Problem with GCC as a Scheme compiler: tail calls Mark H Weaver
2011-04-07 14:37 ` Noah Lavine
2011-04-11 22:31 ` Andy Wingo
2011-04-11 23:12 ` Noah Lavine
2011-04-07 10:43 ` Hi! Interested in GSoC. Feedback on these ideas? Andreas Rottmann
2011-04-07 13:21 ` Paul Raccuglia
2011-04-07 21:45 ` Paul Raccuglia
2011-04-08 0:01 ` Paul Raccuglia
2011-04-08 1:00 ` dsmich
2011-04-08 4:36 ` Paul Raccuglia
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=BANLkTimX0+-0uVf-LJxi9_0fX7EMXLthWQ@mail.gmail.com \
--to=noah.b.lavine@gmail.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.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).