unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: compile-rtl, II
Date: Mon, 21 Jan 2013 20:08:15 +0100	[thread overview]
Message-ID: <CAGua6m36SFXDnt1kJWkyh9nURG66pOngnE7uv4RBsDtRf6d9Lg@mail.gmail.com> (raw)
In-Reply-To: <87ip6q4erd.fsf@pobox.com>

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

On Mon, Jan 21, 2013 at 6:39 PM, Andy Wingo <wingo@pobox.com> wrote:

> On Mon 15 Oct 2012 16:05, Stefan Israelsson Tampe <stefan.itampe@gmail.com>
> writes:
>
> > (arg1, return-address, old-frame, program, arg2 ...)
> >
> > This way we do not need to copy the program field at a tail call
>
> What would you do for 0 arguments?
>
> I would just fill in the first argument with SCM_UNSPECIFIED or such and
send information to the call that
0 argumnets is filled in, then the compiled code would work smartly and use
this field for normal rtl registers.
Ayway I did not pursue this at date more than adding some flags to the
compiler so that we can turn on this
feature and try it out later.


> > Also another kind of difficulty will arise, many instructions only
> > take a value of 256 register positions
>
> Do you have examples?  I think the idea I had in mind was to reserve the
> last two or three of the 8-bit-addressable registers as temporaries, and
> emit long-mov shuffles to handle those cases.
>
> To be frank it looks like 95% of the code will never need to think about
this issue, so your approach seams sane.


> Andy
> --
> http://wingolog.org/
>

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

      reply	other threads:[~2013-01-21 19:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-15 14:05 compile-rtl, II Stefan Israelsson Tampe
2013-01-21 17:39 ` Andy Wingo
2013-01-21 19:08   ` Stefan Israelsson Tampe [this message]

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=CAGua6m36SFXDnt1kJWkyh9nURG66pOngnE7uv4RBsDtRf6d9Lg@mail.gmail.com \
    --to=stefan.itampe@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.com \
    /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).