ARM: Be consistent about the condition codes used with CompareObjectType
authorsgjesse@chromium.org <sgjesse@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 1 Jun 2011 08:54:30 +0000 (08:54 +0000)
committersgjesse@chromium.org <sgjesse@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 1 Jun 2011 08:54:30 +0000 (08:54 +0000)
commitbbfd202c8183f09f25e4ff3236ad2e2ee57d0871
treec2010f56dd58c95404eac8ae55cc353001bb4c84
parent955e6a2496b81cbf4f5d8818d048db13eceb273c
ARM: Be consistent about the condition codes used with CompareObjectType

Now the signed comparison condition codes are always used with CompareObjectType. The type is only a byte and ldrb will do sign extension, so signed and unsigned comparison will give the same result. Signed condition codes are easier to read.

R=erik.corry@gmail.com

BUG=none
TEST=none

Review URL: http://codereview.chromium.org//7104019

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8134 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/arm/stub-cache-arm.cc