option --prof documentation help added#34991
Conversation
|
I think you need to add it to With that being said, I'm still opposed to adding any V8 options as Node.js options (which is what this PR is doing) for the reasons outlined here: #34281 (comment) and #34281 (comment). If the goal is to have |
Hi @mmalecki thank you for you answer, I thought something similar, but I just searched other option help into [ |
src/node_options.cc
Outdated
| + "Generate V8 profiler output.", | ||
| + &EnvironmentOptions::syntax_prof_only); |
There was a problem hiding this comment.
| + "Generate V8 profiler output.", | |
| + &EnvironmentOptions::syntax_prof_only); | |
| "Generate V8 profiler output.", | |
| V8Option{}); |
There was a problem hiding this comment.
hello @addaleax I added your suggested change but when I running test show the following error:
../src/node_options.cc:405:1: error: invalid argument type 'node::options_parser::OptionsParser<node::EnvironmentOptions>::V8Option' to unary expression V8Option{});
thanks for you help :)
There was a problem hiding this comment.
@Krank2me As you can see, the Github actions fail because this code currently doesn’t compile – if I apply the suggestion here, it passes locally for me.
If you are having trouble with this, it might be good if you could upload the relevant parts of the compile output somewhere
There was a problem hiding this comment.
@addaleax you're right, thank you so much for you help :)
addaleax
left a comment
There was a problem hiding this comment.
@mmarchini We do already document a few V8 flags this way, in particular --abort-on-uncaught-exception, --disallow-code-generation-from-strings, --huge-max-old-generation-size and --jitless – I think that’s fair
|
--abort-on-uncaught-exception is documented because we have specific behavior on Node.js (it's more of a hybrid flag today instead of a purely V8 flag), and the other flags seem safer/more stable than --prof (V8 has explicitly said to us many times that this flag is not supported and could break at any point). I don't feel strong enough about it to block, but I still think we should at the very least differentiate V8 flags from Node.js flags in our documentation (doesn't need to be implemented in this PR though) |
PR-URL: #34991 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Juan José Arboleda <[email protected]>
|
landed in eb24573 , thanks for the contribution! 🎉 |
PR-URL: #34991 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Juan José Arboleda <[email protected]>
PR-URL: #34991 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Juan José Arboleda <[email protected]>
PR-URL: #34991 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Juan José Arboleda <[email protected]>
PR-URL: #34991 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Juan José Arboleda <[email protected]>
Hi, I trying to add prof documentation help on node_options.cc file, but when I test running show the following error:
../src/node_options.cc:405:35: error: no member named 'syntax_prof_only' in
'node::EnvironmentOptions'
&EnvironmentOptions::syntax_prof_only);
So I don't know if I have to add 'syntax_prof_only' somewhere before.
Thaks for you help
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes