Status: Accepted Owner: [email protected] Labels: Type-FeatureRequest Priority-Medium CodeGenerator
New issue 210 by [email protected]: Avoid silly jumps on backward CFG edges http://code.google.com/p/v8/issues/detail?id=210 Merge code at backward CFG edges is emitted right at the end of the predecessor block. For branches, this means that we negate the condition and emit the merge code as fall-through, followed by an unconditional backward jump to the successor label, followed by binding the branch target for the effective fall-through. In the case of empty merge code, we branch around an unconditional jump. By computing the merge code first, we can avoid this. More difficult to implement, but potentially worth doing, is that we can reuse any forward merge code at the block for the backward edge. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev -~----------~----~----~----~------~----~------~--~---
