Changes between Version 28 and Version 29 of CottoTasklist

Timestamp:

10/13/10 01:50:20 (11 years ago)

Author:

cotto

Comment:

--

CottoTasklist

@@ -4 +4 @@
  - Take a shot at implementing one-pass lazy PMC class initialization.
  - http://irclog.perlgeek.de/parrot/2010-06-20#i_2460692
- - Make the [wiki:Deprecation Deprecation] page not suck
-   - troll through svn logs and fill in what needs to be done
  - add stuff from http://irclog.perlgeek.de/parrot/2010-05-28#i_2378589 to LoritoRoadmap
  - Add a test for #1652 to t/profiling/profiling.t
@@ -15 +13 @@
      - docs/parrotbyte.pod duplicates some of pdd13.  Merge parrotbyte.pod into the pdd.  It's hard enough to keep one document up-to-date.
      - It'd also be nice to speed up Parrot_Sub_get_line_from_pc since it currently eats about 15% of the processing time *after* caching its results.  Knowing PackFiles might help.
- - test profiling output (pprof format)
  - test pprof to callgrind conversion and callgrind-style output
  - Create an efficient binary output format with optional compression, similar to NYTProf.
    - Alternately, consider moving the Callgrind output code into the profiling runcore and using the pprof output only for testing.
    - Look into spitting out NYTProf-compatible output too.
- - Optimize the profiling runloop code.  Major refactors should wait until some tests are in place.
+ - Profile/optimize the profiling runloop code.
 
 
 == todo (would be nice): ==
- - Fix CLI argument parsing so that options can be passed to the profiling runcore.
-   - It'd also be nice if parrot were smart enough to treat -Rp or -Rprof to the same as -Rprofiling
-     - This is a trivial change to compilers/imcc/main.c
  - Switch to a Configure.pl-based approach for finding the appropriate timing functions.
 
@@ -32 +26 @@
  - Make docs/dev/profiling.pod helpful to a (hypothetical) annoyed and scared newbie.
  - Figure out what to test. (see [wiki:TestingProfiling])
- - Write some fake tests to figure out what the profiling testing interface should look like.
  - pprof2cg (split into a module, test individual components, multiple output formats (when implemented))
    - 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.
@@ -41 +34 @@
   - profiling a pbc without line information (if possible)
   - proper namespace support
-  - threads
+  - threads (should parrot get proper threading)
  - make profiler useful to HLLs (nqp especially, pge would be helpful too)
   - time spent per sub/method would be very helpful to pmichaud