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@gnu.org
Subject: wip-rtl extra space at allocation of frame at call's
Date: Sun, 12 Aug 2012 23:05:37 +0200	[thread overview]
Message-ID: <CAGua6m1r0P5XWK9vnK-_EMQf2afqhjE_+fSi7VvwQWdgf_AgnQ@mail.gmail.com> (raw)

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

Hi,

Currently if we want to compile to native code in the rtl branch the call
instruction is very heave to inline
directly. I would like to, when the number of arguments is less then 20
arguments jump to global code segment
where all the nessesary heavy lifting is done. Else the whole call
instruction can go in. So the issue here is that
I would like to move the alloc-frame part of the call instruction out to
the general code and simply just add the argumet's to their place and then
jump to this global code. The problem is that we need to check the stack
space before jumping and this checking is quite wordy and I would like to
keep the size if the inlined code small.

Therefore I suggest that always when we allocate stack space we take out 20
extra slots in the check, meaning that we do not need to check for these
slot's when the call.

At least that's what I plan to do in the native compilation.

Any other ideas?

/Stefan

>
>

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

                 reply	other threads:[~2012-08-12 21:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAGua6m1r0P5XWK9vnK-_EMQf2afqhjE_+fSi7VvwQWdgf_AgnQ@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).