Skip to content

deps: backport 224d376 from V8 upstream - #10546

Closed
jBarz wants to merge 1 commit into
nodejs:v6.x-stagingfrom
jBarz:v8_new_delete_v6
Closed

deps: backport 224d376 from V8 upstream#10546
jBarz wants to merge 1 commit into
nodejs:v6.x-stagingfrom
jBarz:v8_new_delete_v6

Conversation

@jBarz

@jBarzjBarz commented Dec 30, 2016

Copy link
Copy Markdown
Contributor
Checklist
  • make -j4 test (UNIX)
  • commit message follows commit guidelines
Affected core subsystem(s)

v8

@nodejs-github-botnodejs-github-bot added v6.x v8 engine Issues and PRs related to the V8 dependency. labels Dec 30, 2016
@MylesBorins

MylesBorins commented Dec 30, 2016

Copy link
Copy Markdown
Contributor

@jBarz can you squash the patch bump into the first commit please

@MylesBorins

Copy link
Copy Markdown
Contributor

@jBarzjBarz changed the title deps: cherry-pick 224d37 from V8 upstreamdeps: backport 224d376 from V8 upstreamJan 18, 2017
Orignial commit message:
Abort in delete operators that shouldn't be called.
Section 3.2 of the C++ standard states that destructor
definitions implicitly "use" operator delete functions.
Therefore, these operator delete functions must be
defined even if they are never called by user code
explicitly.
http://www.open-std.org/JTC1/SC22/WG21/docs/
cwg_defects.html#261
gcc allows them to remain as empty definitions. However,
not all compilers allow this. (e.g. xlc on zOS). This pull
request creates definitions which if ever called, result
in an abort.
R=danno@chromium.org,jochen@chromium.org
BUG=
LOG=N
Review-Url: https://codereview.chromium.org/2588433002
Cr-Commit-Position: refs/heads/master@{nodejs#41981}
@jBarz

Copy link
Copy Markdown
ContributorAuthor

Just change the commit message to say backport instead of cherry-pick

@jasnelljasnell 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.

rubber stamp LGTM

@MylesBorins

Copy link
Copy Markdown
Contributor

MylesBorins pushed a commit that referenced this pull request Jan 24, 2017
Orignial commit message:
Abort in delete operators that shouldn't be called.
Section 3.2 of the C++ standard states that destructor
definitions implicitly "use" operator delete functions.
Therefore, these operator delete functions must be
defined even if they are never called by user code
explicitly.
http://www.open-std.org/JTC1/SC22/WG21/docs/
cwg_defects.html#261
gcc allows them to remain as empty definitions. However,
not all compilers allow this. (e.g. xlc on zOS). This pull
request creates definitions which if ever called, result
in an abort.
R=danno@chromium.org,jochen@chromium.org
BUG=
LOG=N
Review-Url: https://codereview.chromium.org/2588433002
Cr-Commit-Position: refs/heads/master@{#41981}
PR-URL: #10546
Reviewed-By: James M Snell <jasnell@gmail.com>
@MylesBorins

Copy link
Copy Markdown
Contributor

landed in 6d3f82c

MylesBorins pushed a commit that referenced this pull request Jan 24, 2017
Orignial commit message:
Abort in delete operators that shouldn't be called.
Section 3.2 of the C++ standard states that destructor
definitions implicitly "use" operator delete functions.
Therefore, these operator delete functions must be
defined even if they are never called by user code
explicitly.
http://www.open-std.org/JTC1/SC22/WG21/docs/
cwg_defects.html#261
gcc allows them to remain as empty definitions. However,
not all compilers allow this. (e.g. xlc on zOS). This pull
request creates definitions which if ever called, result
in an abort.
R=danno@chromium.org,jochen@chromium.org
BUG=
LOG=N
Review-Url: https://codereview.chromium.org/2588433002
Cr-Commit-Position: refs/heads/master@{#41981}
PR-URL: #10546
Reviewed-By: James M Snell <jasnell@gmail.com>
@MylesBorinsMylesBorins mentioned this pull request Jan 24, 2017
@jBarz
jBarz deleted the v8_new_delete_v6 branch January 24, 2017 17:11
@jBarzjBarz mentioned this pull request Jan 28, 2017
2 tasks
MylesBorins pushed a commit that referenced this pull request Jan 31, 2017
Orignial commit message:
Abort in delete operators that shouldn't be called.
Section 3.2 of the C++ standard states that destructor
definitions implicitly "use" operator delete functions.
Therefore, these operator delete functions must be
defined even if they are never called by user code
explicitly.
http://www.open-std.org/JTC1/SC22/WG21/docs/
cwg_defects.html#261
gcc allows them to remain as empty definitions. However,
not all compilers allow this. (e.g. xlc on zOS). This pull
request creates definitions which if ever called, result
in an abort.
R=danno@chromium.org,jochen@chromium.org
BUG=
LOG=N
Review-Url: https://codereview.chromium.org/2588433002
Cr-Commit-Position: refs/heads/master@{#41981}
PR-URL: #10546
Reviewed-By: James M Snell <jasnell@gmail.com>
@mscdexmscdex mentioned this pull request Mar 21, 2017
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

@jBarz@MylesBorins@jasnell@nodejs-github-bot