Closed
Bug 1645464
Opened 5 years ago
Closed 5 years ago
Use a single set of ProfilerCategory definitions
Categories
(Core :: Gecko Profiler, task, P3)
Core
Gecko Profiler
Tracking
()
RESOLVED
FIXED
mozilla79
Tracking | Status | |
---|---|---|
firefox79 | --- | fixed |
People
(Reporter: tcampbell, Assigned: tcampbell)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Right now we duplicate profiler categories in js/public/ProfilingCategory.h
and mozglue/baseprofiler/public/BaseProfilingCategory.h
. I think we can reasonably share the definition without disturbing too much.
Proposal:
- Move the list to
mozglue/baseprofiler/public/ProfilingCategoryList.h
- Add this to the
moz.build
EXPORTS
list for both js/src and mozglue/baseprofiler. - Rename the macro to
MOZ_PROFILING_CATEGORY_LIST
This generates two copies in the build output, but there is only the single macro in it and header guards do the right thing.
Note that standalone SpiderMonkey bundles already include the baseprofiler source in their tarball.
Assignee | ||
Comment 1•5 years ago
|
||
Replace the duplicate lists in mozglue/baseprofiler/public and js/public with
a shared list. Add this list to both moz.build files so it is published twice
which simplifies supporting different standalone configurations.
Thank you so much for doing this (I wouldn't have known about the EXPORTS
thing!)
Pushed by tcampbell@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/7c59c362decc
Use a shared ProfilingCategoryList.h r=gerald,froydnj
Comment 4•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox79:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla79
You need to log in
before you can comment on or make changes to this bug.
Description
•