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

Issue 223623003: Fix fixed-point vcvt_f64_s32 immediate value encoding (Closed)

Created:
6 years, 8 months ago by oetuaho-nv
Modified:
6 years, 8 months ago
Reviewers:
ulan, Jarin, jbramley, rmcilroy
CC:
v8-dev
Base URL:
git://github.com/v8/v8.git@master
Visibility:
Public.

Description

Fix fixed-point vcvt_f64_s32 immediate value encoding The (32 - fraction_bits) value should be encoded so that the least significant bit is set to bit 5 and the four next bits to bits 0-3. Fix the previously incorrect encoding. This bug did not cause behavioral issues before, since in existing uses of the function the order of the bits in the immediate value does not matter, as they are all 1. BUG=3256 LOG=N R=ulan@chromium.org Committed: https://code.google.com/p/v8/source/detail?r=20508

Patch Set 1 #

Total comments: 2

Patch Set 2 : Reorder bits for clarity #

Unified diffs Side-by-side diffs Delta from patch set Stats (+9 lines, -8 lines) Patch
M src/arm/assembler-arm.cc View 1 chunk +3 lines, -2 lines 0 comments Download
M src/arm/disasm-arm.cc View 1 1 chunk +1 line, -1 line 0 comments Download
M src/arm/simulator-arm.cc View 1 1 chunk +1 line, -1 line 0 comments Download
M test/cctest/test-assembler-arm.cc View 1 chunk +2 lines, -2 lines 0 comments Download
M test/cctest/test-disasm-arm.cc View 1 chunk +2 lines, -2 lines 0 comments Download

Messages

Total messages: 10 (0 generated)
oetuaho-nv
Spun off bugfix part from https://codereview.chromium.org/222403002/ since the optimization is likely to take a different ...
6 years, 8 months ago (2014-04-03 17:59:55 UTC) #1
rmcilroy
+ulan Seems reasonable to me, but adding Ulan to check as well. https://codereview.chromium.org/223623003/diff/1/src/arm/disasm-arm.cc File src/arm/disasm-arm.cc ...
6 years, 8 months ago (2014-04-03 18:59:10 UTC) #2
ulan
On 2014/04/03 18:59:10, rmcilroy wrote: > +ulan > > Seems reasonable to me, but adding ...
6 years, 8 months ago (2014-04-04 09:30:14 UTC) #3
oetuaho-nv
Patch set 2 addressed the comments, committing.
6 years, 8 months ago (2014-04-04 10:17:13 UTC) #4
oetuaho-nv
The CQ bit was checked by oetuaho@nvidia.com
6 years, 8 months ago (2014-04-04 10:17:17 UTC) #5
commit-bot: I haz the power
The CQ bit was unchecked by commit-bot@chromium.org
6 years, 8 months ago (2014-04-04 10:20:07 UTC) #6
commit-bot: I haz the power
Commit queue rejected this change because it did not recognize the base URL. Please commit ...
6 years, 8 months ago (2014-04-04 10:20:08 UTC) #7
oetuaho-nv
Looks like commit bot is rejecting the change. I used instructions from https://github.com/v8/v8/wiki/Proposing-a-Patch Are they ...
6 years, 8 months ago (2014-04-04 10:38:45 UTC) #8
rmcilroy
On 2014/04/04 10:38:45, oetuaho-nv wrote: > Looks like commit bot is rejecting the change. I ...
6 years, 8 months ago (2014-04-04 10:55:39 UTC) #9
rmcilroy
6 years, 8 months ago (2014-04-04 11:12:48 UTC) #10
Message was sent while issue was closed.
Committed patchset #2 manually as r20508 (presubmit successful).

Powered by Google App Engine
This is Rietveld 408576698