This is the mail archive of the
mailing list for the GCC project.
Re: Help with implementing Wine optimization experiment
- From: Jeff Law <law at redhat dot com>
- To: Trevor Saunders <tbsaunde at tbsaunde dot org>, Daniel Santos <daniel dot santos at pobox dot com>
- Cc: gcc <gcc at gcc dot gnu dot org>
- Date: Sun, 14 Aug 2016 18:16:28 -0600
- Subject: Re: Help with implementing Wine optimization experiment
- Authentication-results: sourceware.org; auth=none
- References: <firstname.lastname@example.org> <20160814075547.btzb6obkhjc7pzsx@ball>
On 08/14/2016 01:57 AM, Trevor Saunders wrote:
Right. That's what I've done with out-of-line prologues/epilogues in
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
3. Add the two routines somewhere so that they are linked into the output.
I think you want to put those into libgcc then.