they (v8) did have a (documented?) promise that they would consider Node's compatibility as a major factor while implementing features?

@gireeshpunathil i'm pretty sure they don't consider this an issue with compat considering Node.js was piping straight through to V8's own bespoke option; we also already gate some --perf-prof options to linux, as you can see in the testfile, owing to similar changes upstream.

--perf-prof doesn't make much sense on outside of Linux, as it generates a jitdump file.

--perf-basic-prof on the other hand could be used on other platforms, since it is just a text file (I have used it on OS X in the past). Well, that's not really a Node.js issue though. I'll get in touch with V8 about that.

thanks @mmarchini 🙇‍♀

ok, thanks @mmarchini, that will really help!

for the context, my use case is here: https://github.com/nodejs/diagnostics/tree/master/documentation/profiling - attempt to document diagnostic best practices around profiling. These are aimed at user-journey driven, endorsed by node project, and planned to be supported for long term.

as that is a conversation with v8, and this PR is just documenting the code behavior that was uncovered in the field, it looks good to me!

CI: https://ci.nodejs.org/job/node-test-pull-request/29297/

Landed in 72b6cea