Turn UInt32 analysis into a proper HPhase.

Turn UInt32 analysis into a proper HPhase.

R=jkummerow@chromium.org

Committed: https://code.google.com/p/v8/source/detail?r=15441

[Jakob Kummerow, 2013-07-02 09:16:40]

LGTM. While you're here, you can fix a few typos :-)

https://codereview.chromium.org/18487003/diff/1/src/hydrogen-uint32-analysis.cc
File src/hydrogen-uint32-analysis.cc (right):

https://codereview.chromium.org/18487003/diff/1/src/hydrogen-uint32-analysis....
src/hydrogen-uint32-analysis.cc:67: // Encountered phis are optimisitically
treated as safe uint32 uses,
nit: optimistically

https://codereview.chromium.org/18487003/diff/1/src/hydrogen-uint32-analysis....
src/hydrogen-uint32-analysis.cc:69: // path will be performed later by
UnmarkUnsafePhis to clear kUint32 from
nit: s/path/pass/

https://codereview.chromium.org/18487003/diff/1/src/hydrogen-uint32-analysis....
src/hydrogen-uint32-analysis.cc:70: // phis that are not actually uint32-safe
(it requries fix point iteration).
nit: requires

https://codereview.chromium.org/18487003/diff/1/src/hydrogen-uint32-analysis....
src/hydrogen-uint32-analysis.cc:78: // There is a phi use of this value from a
phis that is not yet
nit: "from a phi that..."

https://codereview.chromium.org/18487003/diff/1/src/hydrogen-uint32-analysis....
src/hydrogen-uint32-analysis.cc:96: // There is a phi use of this value from a
phis that is not yet
nit: "from a phi that..."

https://codereview.chromium.org/18487003/diff/1/src/hydrogen-uint32-analysis....
src/hydrogen-uint32-analysis.cc:119: // Lazyly mark constants that fit into
uint32 range with kUint32 flag.
nit: Lazily

https://codereview.chromium.org/18487003/diff/1/src/hydrogen-uint32-analysis....
src/hydrogen-uint32-analysis.cc:190: // Check if any operands to safe phies were
unmarked
nit: s/phies/phis/

[Benedikt Meurer, 2013-07-02 10:53:14]

Committed patchset #2 manually as r15441 (presubmit successful).