Simply to investigate what RegExp is taking long time in several JetStream2 benchmarks.
After looking into the current SamplingProfiler and RegExp code, I think maybe, we should take a very simple way that is previously done in the previous patch because,
1. Yarr RegExp JIT code is not following JS calling-convention right now. And if we want to do that, we need to execute Yarr RegExp through LLInt vmEntry, it is not desirable.
2. RegExp JIT code must be a leaf of execution in terms of SamplingProfiler. So, just recording in VM is enough.
Created attachment 378721 [details]
Created attachment 433646 [details]
Comment on attachment 433646 [details]
Committed r279976 (239719@main): <https://commits.webkit.org/239719@main>
*** Bug 190336 has been marked as a duplicate of this bug. ***