another idea: How about splitting Canonicalize phase into two (e.g.
CanonicalizeEarly and CanonicalizeLate)? There are potentially more things
that
depend on later optimization passes and it would be more a general solution
than
patching up the range analysis.
https://chromiumcodereview.appspot.com/10411016/diff/1/src/hydrogen.cc
File src/hydrogen.cc (right):
https://chromiumcodereview.appspot.com/10411016/diff/1/src/hydrogen.cc#newcode1112
src/hydrogen.cc:1112: || !value->HasRange());
Can't you just check HasRange() here and leave it alone if there is an
exisiting range calculated?
https://chromiumcodereview.appspot.com/10411016/
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
