Changes between Initial Version and Version 1 of CottoTasklist

12/05/09 08:55:42 (12 years ago)

initial version


  • CottoTasklist

    v1 v1  
     1This page is a personal todo list for me, cotto.  Others are welcome to take on any tasks mentioned here, but the primary purpose for this page is to keep track of what I intend to do.  Because of that, I haven't spend much effort on breaking tasks down into bite-size chunks or made much of a concrete plan.  If you are interested in helping but don't know where to start, catch me on #parrot and I'll put you to work.   
     4 - test profiling output (pprof format) 
     5 - test pprof to callgrind conversion and callgrind-style output 
     6 - Figure out a nice way to integrate annotations into the profile. 
     7 - Switch to a approach for finding the appropriate timing functions. 
     8 - Create an efficient binary output format with optional compression, similar to NYTProf. 
     9 - Optimize the profiling runloop code.  It are slow. 
     10 - Consider moving the Callgrind output code into the profiling runcore. 
     11 - Abstract output in the profiling runcore to minimize the amount of code that cares about the output format. 
     12 - Fix CLI argument parsing so that options can be passed to the profiling runcore. 
     13   - It'd also be nice if parrot were smart enough to treat -Rp or -Rprof to the same as -Rprofiling . 
     16 * What are "basic blocks" in Callgrind's format?  Callgrind's docs aren't at all helpful here.  RTFS applies. 
     19profiling testing todo: 
     20 - figure out what to test 
     21 - actual profiling runcore output (does it work, is the output valid) 
     22 - pprof2cg (split into a module, test individual components, multiple output formats (when implemented)) 
     23   - The Callgrind output code may end up in C since nqp is way too slow and even the Perl 5 version isn't very fast.  This would make testing more interesting, though I'd still have a way to produce either the pprof or the callgrind formatted output. 
     24 - stats output should also be tested since it's nice for debugging (note to self: ???) 
     25 - specific test cases 
     26  - stupid hello world 
     27  - profiling a pbc without line information (if possible)