Skip to content

deps: cherry-pick 866ee63 from upstream V8 - #13630

Closed
targos wants to merge 1 commit into
nodejs:masterfrom
targos:backport-split-fix
Closed

deps: cherry-pick 866ee63 from upstream V8#13630
targos wants to merge 1 commit into
nodejs:masterfrom
targos:backport-split-fix

Conversation

@targos

Copy link
Copy Markdown
Member

Original commit message:

[string] Re-enable result caching for String.p.split
Runtime::kStringSplit's result caching is only enabled when limit equals
kMaxUInt32.
BUG=v8:6463
Review-Url: https://codereview.chromium.org/2923183002
Cr-Commit-Position: refs/heads/master@{#45724}

Fixes: #13445

@nodejs/v8

I did not update V8_PATCH_LEVEL because V8 5.9 is still supported.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines
Affected core subsystem(s)

V8

Original commit message:
[string] Re-enable result caching for String.p.split
Runtime::kStringSplit's result caching is only enabled when limit equals
kMaxUInt32.
BUG=v8:6463
Review-Url: https://codereview.chromium.org/2923183002
Cr-Commit-Position: refs/heads/master@{nodejs#45724}
Fixes: nodejs#13445
@nodejs-github-botnodejs-github-bot added the v8 engine Issues and PRs related to the V8 dependency. label Jun 12, 2017
@targos

Copy link
Copy Markdown
MemberAuthor

Ping @nodejs/v8

@bnoordhuisbnoordhuis left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I suppose, but is there a reason why this hasn't been back-ported upstream?

@targos

Copy link
Copy Markdown
MemberAuthor

It has been backported to 6.0 only.

Quoting @bmeurer:

Since the fix is trivial, it might be worth considering to cherry-pick this into Node master (which is now at 5.9).

@bmeurer

Copy link
Copy Markdown
Member

LGTM, cc @schuay

@targos

Copy link
Copy Markdown
MemberAuthor

@targos

Copy link
Copy Markdown
MemberAuthor

Thank you. Landed in 7cdcca7

@targostargos closed this Jun 20, 2017
@targos
targos deleted the backport-split-fix branch June 20, 2017 13:26
targos added a commit that referenced this pull request Jun 20, 2017
Original commit message:
[string] Re-enable result caching for String.p.split
Runtime::kStringSplit's result caching is only enabled when limit equals
kMaxUInt32.
BUG=v8:6463
Review-Url: https://codereview.chromium.org/2923183002
Cr-Commit-Position: refs/heads/master@{#45724}
PR-URL: #13630Fixes: #13445
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

v8 engineIssues and PRs related to the V8 dependency.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@targos@bmeurer@bnoordhuis@nodejs-github-bot