Mercurial > hg > graal-jvmci-8
comparison ProblemsIdeas.txt @ 3229:4a6bda6cfe28
Fix for usages that are phi in rematerialization
author | Gilles Duboscq <gilles.duboscq@oracle.com> |
---|---|
date | Thu, 21 Jul 2011 11:32:22 +0200 |
parents | 8793d44991fd |
children | e3d3fd5b638a |
comparison
equal
deleted
inserted
replaced
3228:b95c8fa99e8c | 3229:4a6bda6cfe28 |
---|---|
74 | 74 |
75 This could be done in the context of a more advanced induction varaible analysis to be able to detect such access patterns. In this example we removed 2 array access (2 loads + 2 address computation + 2 bounds checks if not hoisted) while only adding 2 moves (phis) | 75 This could be done in the context of a more advanced induction varaible analysis to be able to detect such access patterns. In this example we removed 2 array access (2 loads + 2 address computation + 2 bounds checks if not hoisted) while only adding 2 moves (phis) |
76 | 76 |
77 | 77 |
78 * Implement array bounds check elimination | 78 * Implement array bounds check elimination |
79 | |
80 * Rematerialize only the nodes that were affected by GVN | |
81 This will probably require something that tracks changes to the Graph, the cost of such a tracking should be evaluated |