tools: hide symbols for builtin JS files in binary #20634
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Do not expose symbols like `node::internal_process_next_tick_value`, `node::internal_process_next_tick_key` in the created `node` binary by wrapping them in an anonymous namespace.
nodejs-github-bot
added
the
build
jasnell
approved these changes
May 9, 2018
This change is completely internals-only, and at least on my local build these symbols aren’t even external symbols. This is really a pretty minor change here. :) |
devsnek
approved these changes
May 9, 2018
cjihrig
approved these changes
May 9, 2018
bnoordhuis
approved these changes
May 9, 2018
tniessen
approved these changes
May 9, 2018
danbev
approved these changes
May 11, 2018
|
Windows CI re-run: https://ci.nodejs.org/job/node-test-commit-windows-fanned/17899/ |
addaleax
added
the
author ready
TimothyGu
approved these changes
May 11, 2018
|
Landed in 7b39503 |
addaleax
added a commit
that referenced
this pull request
May 14, 2018
Do not expose symbols like `node::internal_process_next_tick_value`, `node::internal_process_next_tick_key` in the created `node` binary by wrapping them in an anonymous namespace. PR-URL: #20634 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Gus Caplan <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: Daniel Bevenius <[email protected]> Reviewed-By: Tiancheng "Timothy" Gu <[email protected]>
addaleax
added a commit
that referenced
this pull request
May 14, 2018
Do not expose symbols like `node::internal_process_next_tick_value`, `node::internal_process_next_tick_key` in the created `node` binary by wrapping them in an anonymous namespace. PR-URL: #20634 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Gus Caplan <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Tobias Nießen <[email protected]> Reviewed-By: Daniel Bevenius <[email protected]> Reviewed-By: Tiancheng "Timothy" Gu <[email protected]>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Do not expose symbols like
node::internal_process_next_tick_value,node::internal_process_next_tick_keyin the creatednodebinaryby wrapping them in an anonymous namespace.
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes