projects / platform / upstream / coreclr.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: cb73944) | patch
JIT: don't overlook strong nearby preference in LSRA (#16028)
authorAndy Ayers <andya@microsoft.com>
Mon, 29 Jan 2018 20:36:38 +0000 (12:36 -0800)
committerGitHub <noreply@github.com>
Mon, 29 Jan 2018 20:36:38 +0000 (12:36 -0800)
commitc3dd2610f0c6963b16ca27843942398271de7760
tree767ab06153cdadb49f5d4f2a990acd931bf1af8ctree | snapshot
parentcb73944d6d159bd02adc29f0588b97f0f76da1a1commit | diff
JIT: don't overlook strong nearby preference in LSRA (#16028)

When allocating an interval, LSRA will look at related intervals
for preference hints.

LSRA may look past a related interval I1 to its related interval
I2 if I1 looks like a simple copy. But if I1 has been previously
allocated then it seems we are often better served using I1's
preferences instead of using I2's.

Addresses some issues seen in #11390.
src/jit/lsra.cpp diff | blob | history
Domain: Dotnet / Core;