Reviewers: iposva, William Hesse, Message: This change affects variable references as rvalues.
If they're in memory, I chose to move them to a register to avoid the issue of multiple virtual frame elements backed by the same in-memory location. I suspect that we will need them in a register quite soon anyway. Instead, we have duplicated registers which will have copy on write semantics. We don't have to deal with that yet, because they are spilled quite soon after. Description: Begin using the virtual frame for variable proxies and slots. Loading a frame-allocated slot (ie, a frame-allocated local or parameter) to the top of the frame causes it te be allocated to a register if it is in memory, and then the register copied to the top of the frame. Please review this at http://codereview.chromium.org/11023 SVN Base: http://v8.googlecode.com/svn/branches/experimental/toiger/ Affected files: M src/codegen-ia32.cc M src/virtual-frame-ia32.h M src/virtual-frame-ia32.cc --~--~---------~--~----~------------~-------~--~----~ v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev -~----------~----~----~----~------~----~------~--~---
