Closed
Bug 491373
Opened 16 years ago
Closed 15 years ago
Need code profiler for WinCE
Categories
(Developer Infrastructure :: Source Code Analysis, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 493427
People
(Reporter: cjones, Unassigned)
References
Details
There is a pathetic dearth of these tools for WinCE. We will probably have to take this on ourselves. We have several approaches - "stopwatch"-style C++ instrumentation Taras has been doing (heavyweight) - assembly instrumentation to count basic block executions (medium weight) - biting the bullet and writing a proper WinCE profiling kernel module (lightweight)
Reporter | ||
Comment 1•16 years ago
|
||
> - biting the bullet and writing a proper WinCE profiling kernel module
> (lightweight)
Oops, by "profiling" I meant "sampling."
Reporter | ||
Comment 3•16 years ago
|
||
(In reply to comment #2) > Similar work is happening in bug 491373 Sorry, you just sent me into an infinite loop.
Comment 4•16 years ago
|
||
(In reply to comment #3) > (In reply to comment #2) > > Similar work is happening in bug 491373 > > Sorry, you just sent me into an infinite loop. Ugh - bug 493427
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Updated•7 years ago
|
Product: Core → Firefox Build System
Updated•2 years ago
|
Product: Firefox Build System → Developer Infrastructure
You need to log in
before you can comment on or make changes to this bug.
Description
•