From: Jeff Law <law@redhat.com>
To: Trevor Saunders <tbsaunde@tbsaunde.org>,
Daniel Santos <daniel.santos@pobox.com>
Cc: gcc <gcc@gcc.gnu.org>
Subject: Re: Help with implementing Wine optimization experiment
Date: Mon, 15 Aug 2016 00:16:00 -0000 [thread overview]
Message-ID: <a852041c-3865-5366-713f-bc7d9c921435@redhat.com> (raw)
In-Reply-To: <20160814075547.btzb6obkhjc7pzsx@ball>
On 08/14/2016 01:57 AM, Trevor Saunders wrote:
> On Sun, Aug 14, 2016 at 01:23:16AM -0500, Daniel Santos wrote:
>> I'm experimenting with ways to optimize wine (x86 target only) and I believe
>> I can shrink wine's total text size by around 7% by outlining the lengthy
>> pro- and epilogues required for ms_abi functions making sysv_abi calls.
>> Theoretically, fewer instruction cache misses will offset the extra 4
>> instructions per function and result in a net performance gain. However, I'm
>> new to the gcc project and a novice x86 assembly programmer as well (have
>> been wanting to work on gcc for a while now!) In short, I want to:
>>
>> 1. Replace the prologue that pushes di, sp and xmm6-15 with a single call to
>> a global "ms_abi_push_regs" routine
>> 2. Replace the epilogue that pops these regs with a jmp to a global
>> "ms_abi_pop_regs" routine
>> 3. Add the two routines somewhere so that they are linked into the output.
>
> I think you want to put those into libgcc then.
Right. That's what I've done with out-of-line prologues/epilogues in
the past.
Jeff
next prev parent reply other threads:[~2016-08-15 0:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-14 6:20 Daniel Santos
2016-08-14 7:46 ` Daniel Santos
2016-08-14 7:49 ` Trevor Saunders
2016-08-15 0:16 ` Jeff Law [this message]
2016-08-15 10:56 ` Richard Biener
2016-08-16 4:21 ` Daniel Santos
2016-08-15 10:47 ` Florian Weimer
2016-08-17 22:56 ` Daniel Santos
2016-08-15 11:36 ` André Hentschel
2016-08-16 3:13 ` Daniel Santos
2016-08-17 23:04 ` Daniel Santos
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=a852041c-3865-5366-713f-bc7d9c921435@redhat.com \
--to=law@redhat.com \
--cc=daniel.santos@pobox.com \
--cc=gcc@gcc.gnu.org \
--cc=tbsaunde@tbsaunde.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).