Changes between Version 26 and Version 27 of CottoTasklist

Timestamp:

08/03/10 22:18:14 (11 years ago)

Author:

cotto

Comment:

clear out completed items, add some new ones

CottoTasklist

@@ -2 +2 @@
 
 == todo (important, in decreasing order): ==
+ - some way to measure how much time is being spent in each nqp-rx subroutine or method? I know we had stuff using kcachegrind at one point, but I could never get it to work much with pge or nqp-rx because it seemed to have difficulty with tailcalls.
  - make --stagestats for PCT::HLLCompiler less noisy
  - Take a shot at implementing one-pass lazy PMC class initialization.
  - http://irclog.perlgeek.de/parrot/2010-06-20#i_2460692
- - Look into a process for GPG signing releases
-   - as a bare minimum, add SHA1 (or better) checksums of the tarballs to the release announcement
-   - get feedback from #ps folks, update release_manager_guide.pod et al
  - Make the [wiki:Deprecation Deprecation] page not suck
-   - add sub-pages for migration between subsequent supported releases
    - troll through svn logs and fill in what needs to be done
-   - make such updates a *required* *non-optional* *you-will-get-yelled-at-if-you-forget-this* part of the deprecation cycle
-   - see if Coke, kthakore and the Rakudo hackers get less crabby
- - Look at khairul's code:
-   - look through meeting log, add tasks to this todo list
  - 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
@@ -24 +17 @@
      - 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.
- - ~~Figure out how to properly fix pbc_merge (TT #1419)~~
-   - Once this is working, pir files can be compiled to individual pbc files and be merged similar to how C code is compiled.
-   - This will make dependency tracking for pir code much more reliable.
- - Add --hash-seed=xxx to parrot so that hash order-related failures can be diagnosed more quickly.  [http://irclog.perlgeek.de/parrot/2009-12-18#i_1853127 Coke] recently ran a case where this would have made life easier. (submitted in tt #1383)
  - test profiling output (pprof format)
  - test pprof to callgrind conversion and callgrind-style output
@@ -34 +23 @@
    - Look into spitting out NYTProf-compatible output too.
  - Optimize the profiling runloop code.  Major refactors should wait until some tests are in place.
- - ~~Do a code review of r43196.~~
- - ~~Abstract output in the profiling runcore to minimize the amount of code that cares about the output format.~~
- - ~~Figure out a nice way to integrate annotations into the profile.~~
+
 
 == todo (would be nice): ==
@@ -45 +32 @@
 
 == profiling testing todo: ==
- - Make docs/dev/profiling.pod more skimmable.
+ - 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.
@@ -57 +44 @@
   - proper namespace support
   - threads
+ - make profiler useful to HLLs (nqp especially, pge would be helpful too)
+  - time spent per sub/method would be very helpful to pmichaud
+  - deal gracefully with tailcalls
+ - optimize pprof2cg, see [http://irclog.perlgeek.de/parrot/2010-08-03#i_2659752 this] and the ensuing discussion
+
 
 == Questions: ==
- * What are "basic blocks" in Callgrind's format?  Callgrind's docs aren't at all helpful here.  RTFS applies.
+ * What are "basic blocks" in Callgrind's format?  Callgrind's docs aren't at all helpful here.  UTSL applies.
    * A basic block is a straight line piece of code without any branches or branch targets.  It's the smallest individual unit of code to which you can apply a compiler optimization.