You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this is an extension of the initial sharing impl in PR 493257
we should also try to share across:
mem2mem (in particular push-mem, pop-mem, and call-ind)
sub-dword
app instr that reads/writes both whole-bb reg1 and reg2
app instr that does not share same memref: start w/
simple instrs like reg-reg moves by having them use reg2.
initial goal can be this common pattern:
push ebp, mov esp->ebp, push edi, push esi, push ebx
This case also covers improving conflict handling of scratch regs:
/* issue #1590: if our scratch regs are ecx and eax and we have sub-dword memrefs, we
* can't share them, either w/ prior (mi->use_shared) or next (share_addr) inst.
* XXX issue #165: add whole-bb xl8-sharing analysis and measure the usage of the
* 3rd-best scratch reg and if the extra spills+restores will be outweighed
* by the elimination of xl8 we should use edx or ebx as our 1st scratch.
*/
From derek.br...@gmail.com on December 10, 2010 17:58:09
PR 494727
this is an extension of the initial sharing impl in PR 493257
we should also try to share across:
simple instrs like reg-reg moves by having them use reg2.
initial goal can be this common pattern:
push ebp, mov esp->ebp, push edi, push esi, push ebx
Original issue: http://code.google.com/p/drmemory/issues/detail?id=165
The text was updated successfully, but these errors were encountered: