Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(8)

Issue 160452: Fix debug printing of pointers, and a keyed store with smi index error, in X6... (Closed)

Created:
11 years, 4 months ago by William Hesse
Modified:
9 years, 7 months ago
Reviewers:
Lasse Reichstein
CC:
v8-dev
Visibility:
Public.

Description

Fix debug printing of pointers, and a keyed store with smi index error, in X64 Committed: http://code.google.com/p/v8/source/detail?r=2605

Patch Set 1 #

Total comments: 7

Patch Set 2 : '' #

Unified diffs Side-by-side diffs Delta from patch set Stats (+16 lines, -15 lines) Patch
M src/string-stream.h View 1 2 chunks +4 lines, -12 lines 0 comments Download
M src/string-stream.cc View 1 2 chunks +8 lines, -1 line 0 comments Download
M src/x64/ic-x64.cc View 1 2 chunks +4 lines, -1 line 0 comments Download
M test/cctest/cctest.status View 1 1 chunk +0 lines, -1 line 0 comments Download

Messages

Total messages: 4 (0 generated)
William Hesse
11 years, 4 months ago (2009-07-31 13:05:16 UTC) #1
Lasse Reichstein
LGTM http://codereview.chromium.org/160452/diff/1/5 File src/string-stream.cc (right): http://codereview.chromium.org/160452/diff/1/5#newcode172 Line 172: EmbeddedVector<char, 28> formatted; 28 seems like overkill. ...
11 years, 4 months ago (2009-07-31 14:31:07 UTC) #2
Lasse Reichstein
http://codereview.chromium.org/160452/diff/1/4 File src/x64/ic-x64.cc (right): http://codereview.chromium.org/160452/diff/1/4#newcode429 Line 429: __ movl(rbx, rbx); // Clear the high bits ...
11 years, 4 months ago (2009-07-31 15:17:12 UTC) #3
William Hesse
11 years, 4 months ago (2009-08-03 11:52:20 UTC) #4
http://codereview.chromium.org/160452/diff/1/5
File src/string-stream.cc (right):

http://codereview.chromium.org/160452/diff/1/5#newcode172
Line 172: EmbeddedVector<char, 28> formatted;
On 2009/07/31 14:31:07, Lasse Reichstein wrote:
> 28 seems like overkill. If printed as hex, even with a "0x" prefix, it
shouldn't
> take more than 18 bytes.
I was worried that someone would try to print octal values.
I guess we know that won't happen. 20 should be safe: 16 + "0x" + "x" or "-" +
'\0'.

http://codereview.chromium.org/160452/diff/1/4
File src/x64/ic-x64.cc (right):

http://codereview.chromium.org/160452/diff/1/4#newcode428
Line 428: // used as an index in a memory operand.
On 2009/07/31 14:31:07, Lasse Reichstein wrote:
> Where is it checked that it isn't negative?
> (On the other hand, a zero extended negative 32-bit number would be too large
> for use as an index).

It is checked below.

http://codereview.chromium.org/160452/diff/1/4#newcode452
Line 452: __ j(below, &fast);
This test checks that the smi is not negative, and is below the array size, by
using an unsigned comparison.

Powered by Google App Engine
This is Rietveld 408576698