instead of NaCl. For that, we used Emscripten compiler v2.0.7 to compile
the C++ code. Without modifying the C++ code and using the same
optimisation level during compilation, we found that WebAssembly build
is slower than the NaCl build.
To address the performance issue, I wanted to compare the profiling (Instrumentation) result of both the builds using Chrome's Developer Tools. I could gather the profiling data for WebAssembly build. However, I am unable to do the same for NaCl build.
For reference, I have attached WebAssembly profiling result.
Can someone guide me about how to do profiling for NaCl build ? Which flags should be used during compilation and/or at linking stage ? And which tool should be used to do the actual profiling ?
The C++ code is compiled using `pnacl-clang++` compiler. Later `pnacl-transalte` is used to generate the .nexe file. (x86_64 arch)
OS and Compiler details are as follows.
NaCl SDK having `Pepper 50`
Emscripten SDK version 2.0.7
Ubuntu 18.04.5 LTS
Chrome version 86.0.4240.75
Processor : Intel® Core™ i5-5200U CPU @ 2.20GHz × 4
This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.