|
@@ -1495,13 +1495,6 @@ The topic of Chapter~\ref{ch:register-allocation} is implementing a
|
|
|
smarter approach in which we make a best-effort to map variables to
|
|
smarter approach in which we make a best-effort to map variables to
|
|
|
registers, resorting to the stack only when necessary.
|
|
registers, resorting to the stack only when necessary.
|
|
|
|
|
|
|
|
-%% \margincomment{\scriptsize I'm confused: shouldn't `select instructions' do this?
|
|
|
|
|
-%% After all, that selects the x86 instructions. Even if it is separate,
|
|
|
|
|
-%% if we perform `patching' before register allocation, we aren't forced to rely on
|
|
|
|
|
-%% \key{rax} as much. This can ultimately make a more-performant result. --
|
|
|
|
|
-%% Cam}
|
|
|
|
|
-
|
|
|
|
|
-
|
|
|
|
|
Once variables have been assigned to their homes, we can finalize the
|
|
Once variables have been assigned to their homes, we can finalize the
|
|
|
instruction selection by dealing with an idiosyncrasy of x86
|
|
instruction selection by dealing with an idiosyncrasy of x86
|
|
|
assembly. Many x86 instructions have two arguments but only one of the
|
|
assembly. Many x86 instructions have two arguments but only one of the
|
Jeremy Siek