From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: [RFC] proposed change for syscall stub
Date: Wed, 08 Jan 2003 18:32:42 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805643@msgid-missing> (raw)
Jim Hull noticed that I posted the wrong code for the syscall stub:
the one I sent out fits in 5 bundles, not 4 as advertised. The
4-bundle code looks like this:
really_new_syscall_stub:
adds r2 = SYSINFO_OFF, r13;;
ld8 r2 = [r2]
mov r9 = ar.pfs;;
mov r15 = SYSCALL_NR
mov b7 = r2
br.call.sptk.many b6 = b7;;
cmp.eq p6,p0 = -1, r10
mov ar.pfs = r9
(p6) br.cond.spnt.few syscall_error
br.ret.sptk.many rp;;
The only difference here is that we dirty both b6 and b7, which allows
us to remove one stop bit and hence save one bundle. On McKinley,
dirtying more scratch branch registers may impact branch target
address prediction accuracy, but the effect is small enough that I
decided to go for better code-density instead.
--david
next reply other threads:[~2003-01-08 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 18:32 David Mosberger [this message]
2003-01-15 0:53 ` [Linux-ia64] Re: [RFC] proposed change for syscall stub Peter Chubb
2003-01-15 1:11 ` David Mosberger
2003-01-15 1:14 ` Ulrich Drepper
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590709805643@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.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