search for: vregc

...uld thus get any register, causing a MOV. The above trivial example would be reduced by rule R1, so would actually work optimally (because the reduction would account for B's costs in A). However it is trivial to add two or more interfering defs that cause the reduction rule to change to RN: %vregC = def... %vregD = def... %vregB = COPY %R0 %vregA = COPY %vregB = use %vregC, %vregD Now the reduction order is arbitrary and local costs aren't propagated unlike R1 and R2. In fact, there is a rule "RM" proposed by Buchwald [1] that seeks to fix a very similar case to this....

...uld thus get any register, causing a MOV. The above trivial example would be reduced by rule R1, so would actually work optimally (because the reduction would account for B's costs in A). However it is trivial to add two or more interfering defs that cause the reduction rule to change to RN: %vregC = def... %vregD = def... %vregB = COPY %R0 %vregA = COPY %vregB = use %vregC, %vregD I think one idea to improve the situation is to consider the cost vector of adjacent nodes during RN. Let's say you decided to do a RN for node A and want to compute the costs for choosing register %Ri....

...xample would be reduced by rule R1, so would actually >> work optimally (because the reduction would account for B's costs in A). >> However it is trivial to add two or more interfering defs that cause the >> reduction rule to change to RN: >> >> >> >> %vregC = def... >> >> %vregD = def... >> >> %vregB = COPY %R0 >> >> %vregA = COPY %vregB >> >> = use %vregC, %vregD >> >> I think one idea to improve the situation is to consider the cost vector >> of adjacent nodes during RN. Let...

...uld thus get any register, causing a MOV. The above trivial example would be reduced by rule R1, so would actually work optimally (because the reduction would account for B's costs in A). However it is trivial to add two or more interfering defs that cause the reduction rule to change to RN: %vregC = def... %vregD = def... %vregB = COPY %R0 %vregA = COPY %vregB = use %vregC, %vregD I think one idea to improve the situation is to consider the cost vector of adjacent nodes during RN. Let's say you decided to do a RN for node A and want to compute the costs for choosing register %Ri....