Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(115)

Issue 6459051: code review 6459051: runtime: remove unnecessary ROUND in alg.c (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
12 years, 9 months ago by minux1
Modified:
12 years, 9 months ago
Reviewers:
CC:
golang-dev, nigeltao, dave_cheney.net
Visibility:
Public.

Description

runtime: remove unnecessary ROUND in alg.c Introduced in CL 6452046.

Patch Set 1 #

Patch Set 2 : diff -r 175e8ad74055 https://code.google.com/p/go/ #

Total comments: 1

Patch Set 3 : diff -r 175e8ad74055 https://code.google.com/p/go/ #

Unified diffs Side-by-side diffs Delta from patch set Stats (+1 line, -1 line) Patch
M src/pkg/runtime/alg.c View 1 1 chunk +1 line, -1 line 0 comments Download

Messages

Total messages: 6
minux1
Hello golang-dev@googlegroups.com (cc: golang-dev@googlegroups.com), I'd like you to review this change to https://code.google.com/p/go/
12 years, 9 months ago (2012-08-07 01:46:12 UTC) #1
nigeltao
LGTM.
12 years, 9 months ago (2012-08-07 01:48:03 UTC) #2
minux1
Related Russ's comment: http://codereview.appspot.com/6452046/#msg20
12 years, 9 months ago (2012-08-07 01:49:21 UTC) #3
dave_cheney.net
http://codereview.appspot.com/6459051/diff/2001/src/pkg/runtime/alg.c File src/pkg/runtime/alg.c (right): http://codereview.appspot.com/6459051/diff/2001/src/pkg/runtime/alg.c#newcode480 src/pkg/runtime/alg.c:480: ret = (uintptr)(y + t->size); This looks a bit ...
12 years, 9 months ago (2012-08-07 01:49:31 UTC) #4
minux1
*** Submitted as http://code.google.com/p/go/source/detail?r=4bd268b3c88a *** runtime: remove unnecessary ROUND in alg.c Introduced in CL 6452046. ...
12 years, 9 months ago (2012-08-07 01:50:05 UTC) #5
minux1
12 years, 9 months ago (2012-08-07 01:52:17 UTC) #6
On 2012/08/07 01:49:31, dfc wrote:
http://codereview.appspot.com/6459051/diff/2001/src/pkg/runtime/alg.c#newcode480
> src/pkg/runtime/alg.c:480: ret = (uintptr)(y + t->size);
> This looks a bit odd, in essence ret is
>    ret = (unitptr)(x + t->size + t->size);
yes, but we need y anyway, and i try to preserve the original code's structure.
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b