Yes, that's it. Porting the backend (tools/profiler/* and the profiler code in JS) will lay the foundation for the devtools (including the new UI that viktor is working on) and platform profiler. Panos lists the right tests. For JS changes profiling various JS benchmark is a good way to find bugs as well.
On Thu, May 29, 2014 at 8:29 AM, Panos Astithas <[email protected]> wrote: > There are a few different types of tests in various places: > > - browser/devtools/profiler/test contains some tests for the frontend bits > that are currently disabled (bug 973974 - revert that patch locally to > enable them again) > - > toolkit/devtools/server/tests/unit/{test_profiler_actor.js,test_profiler_activation.js} > are a couple of backend tests > - tools/profiler/tests contains low-level SPS API tests > > I've CCed some people who may know more. > > > > On Thu, May 29, 2014 at 10:55 AM, <[email protected]> wrote: >> >> Hi, I have add mips code for built-in-profiler. It could now be used in >> mips platform. such as loongson3A. >> >> It include file in directory: >> --$mozilla_home/browser/devtools/profile; and >> --$mozilla_home/toolkit/crashreporter/google-breakpad >> >> now, although it could be used, I want to kown that if it have some test >> suit that I could test my code more comprehensive. >> >> >> >> 在 2014年5月28日星期三UTC+8下午9时11分33秒，Panos Astithas写道： >> > I'm not familiar with the low-level bits of the profiler, but bug >> > 1007145 >> > >> > sounds relevant: >> > >> > https://bugzilla.mozilla.org/show_bug.cgi?id=1007145 >> > >> > >> > >> > >> > >> > On Wed, May 28, 2014 at 6:19 AM, <[email protected]> wrote: >> > >> > >> > >> > > Rectently, when mips user optimize their html code,they found that the >> > >> > > built-in-profile tool in firefox have not supported. >> > >> > > they use firefox to do optimization just like this article says. >> > >> > > >> > > http://www.oschina.net/translate/performance-optimisation-with-timeline-profiles?cmp&p=2# >> > >> > > >> > >> > > Then, we read the firefox code of the built-in-priofile tool,we >> > > found >> > >> > > the module is divided into two parts: >> > >> > > --the front end is writen by javascript, so it's a >> > >> > > platfrom-undendent code. see directory >> > >> > > $mozilla_home/browser/devtools/profile; >> > >> > > --the back end is writen by c/c++, it's a platform-dependent >> > > code. >> > >> > > now it have not add mips branch. see directory >> > > $mozilla_home/tools/profiler >> > >> > > --and the back end rely on google-breakpad code. it's a >> > >> > > platform-dependent code.see directory >> > >> > > $mozilla_home/toolkit/crashreporter/google-breakpad. now the question >> > > is >> > >> > > :The breakpad code that used in firefox is an older version, have not >> > >> > > support mips platform. but the latest code, have support mips >> > > platform. see >> > >> > > website : https://code.google.com/p/google-breakpad/source/checkout. >> > >> > > >> > >> > > as far as we know, we just find these code associated with this >> > >> > > module. If we want support the build-in-profile tools on mips >> > > platfrom, we >> > >> > > need to transplate the back end code and the google-breakpad code. >> > >> > > now,we want to know,Do your team have found this problem, and >> > > have >> > >> > > transplated this module or to do this. >> > >> > > Thanks. >> > >> > > _______________________________________________ >> > >> > > dev-tech-js-engine-internals mailing list >> > >> > > [email protected] >> > >> > > https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals >> > >> > > >> _______________________________________________ >> dev-tech-js-engine-internals mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals > > _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
