From: David Miller <davem@davemloft.net>
To: rth@twiddle.net
Cc: libffi-discuss@sourceware.org
Subject: Re: [PATCH 3/8] sparc: Rewrite everything
Date: Thu, 30 Oct 2014 04:52:00 -0000 [thread overview]
Message-ID: <20141030.005237.635678277181813551.davem@davemloft.net> (raw)
In-Reply-To: <545151B5.6040103@twiddle.net>
From: Richard Henderson <rth@twiddle.net>
Date: Wed, 29 Oct 2014 13:44:37 -0700
> The one other microarchitecture question I had was wrt call/ret paring.
>
> I was assuming that, for predition purposes, "ret" vs "jmp" must be based on
> the register used -- %i7 or %o7. Thus my call ... jmp %o7+const hopefully
> keeps any call/return prediction stack in sync?
Yes, that should ensure a return address stack prediction hit.
next prev parent reply other threads:[~2014-10-30 4:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 19:46 [PATCH 0/8] Go closures for Sparc Richard Henderson
2014-10-28 19:46 ` [PATCH 7/8] sparc: Add support for Go closures Richard Henderson
2014-10-28 19:46 ` [PATCH 6/8] sparc: Add support for complex types Richard Henderson
2014-10-28 19:46 ` [PATCH 5/8] sparc: Handle more cases of structure return directly Richard Henderson
2014-10-28 19:46 ` [PATCH 8/8] sparc: Re-add abi compliant structure support Richard Henderson
2014-10-28 19:46 ` [PATCH 3/8] sparc: Rewrite everything Richard Henderson
2014-10-29 18:10 ` David Miller
2014-10-29 20:01 ` Richard Henderson
2014-10-29 20:11 ` David Miller
2014-10-29 20:44 ` Richard Henderson
2014-10-30 4:52 ` David Miller [this message]
2014-10-28 19:46 ` [PATCH 1/8] sparc: Eliminate long double ifdefs Richard Henderson
2014-10-28 19:46 ` [PATCH 4/8] sparc: Preprocess float point struct return Richard Henderson
2014-10-28 19:46 ` [PATCH 2/8] sparc: Tidy up symbols Richard Henderson
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=20141030.005237.635678277181813551.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=libffi-discuss@sourceware.org \
--cc=rth@twiddle.net \
/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).