Reviewers: Kasper Lund, iposva, Message: We can do a similar thing at backward unconditional jumps. It would reduce code size, but I'm not sure the effect on compilation time (depending on how many merge blocks there are to compare against (usually not many) vs. how long it takes to compute and emit the code).
The ARM implementation will need to be updated as part of this change. It will be a straight port (or a bit simpler). I'll do it tomorrow morning and send it out for review. Description: Change the way we handle backward jumps in the code generator. Keep the frame states of all the forward-entering frames that had merge code generated. At a backward branch, check if there is no merge code or if we can reuse an existing merge block. Please review this at http://codereview.chromium.org/40169 SVN Base: http://v8.googlecode.com/svn/branches/bleeding_edge/ Affected files: M src/jump-target-ia32.cc M src/jump-target.cc --~--~---------~--~----~------------~-------~--~----~ v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev -~----------~----~----~----~------~----~------~--~---
