From: John L. <mov...@us...> - 2003-06-02 22:59:11
|
Update of /cvsroot/oprofile/oprofile In directory sc8-pr-cvs1:/tmp/cvs-serv7994 Modified Files: ChangeLog TODO Log Message: remove some unused abi code Index: ChangeLog =================================================================== RCS file: /cvsroot/oprofile/oprofile/ChangeLog,v retrieving revision 1.995 retrieving revision 1.996 diff -u -p -d -r1.995 -r1.996 --- ChangeLog 31 May 2003 23:01:15 -0000 1.995 +++ ChangeLog 2 Jun 2003 22:59:04 -0000 1.996 @@ -1,3 +1,13 @@ +2003-06-03 John Levon <le...@mo...> + + * libutil++/child_reader.cpp: + * libabi/abi.cpp: + * libabi/abi.h: + * libabi/abi_test.cpp: + * libabi/op_api.h: + * libabi/op_abi.cpp: + * libabi/op_import.cpp: pedantry, remove unused code + 2003-06-01 Philippe Elie <ph...@wa...> * dae/oprofiled.c: Index: TODO =================================================================== RCS file: /cvsroot/oprofile/oprofile/TODO,v retrieving revision 1.211 retrieving revision 1.212 diff -u -p -d -r1.211 -r1.212 --- TODO 31 May 2003 16:06:43 -0000 1.211 +++ TODO 2 Jun 2003 22:59:04 -0000 1.212 @@ -52,7 +52,7 @@ vma samples cum. samples % o improve the *non* verbose daemon log to be a bit more informative o daemon: opd_put_kernel_samples vs. setup_kernel_sample vs. handle_. Rename, way too confusing o --buffer-size is useless on 2.5 without tuning of watershed - o is --reset racy ? + o is --reset racy ? it's certainly too slow ... o should we make the sighup handler re-read counter config and re-start profiling too ? o improve --smart-demangle o allow user to add it's own pattern in user.pat, document it. @@ -72,12 +72,11 @@ vma samples cum. samples % o allow --ctr0-event to take event numbers. (is it worth ?) o when we dump stats for oprofiled, dump kernel-side values too (for 2.5) o lookup_dcookie can return ENAMETOOLONG but we can't hack it + o remove 2.2 / gcc 2.91 support ? Documentation ------------- - o make distcheck is broken (doc subdir) - o remove dependencies in doc for xmlt.xsl and xhtml-chunk.xls ? o more discussion of problematic code needs to go in the "interpreting" section. o document gcc 2.95 and linenr info problems especially for inline functions o split doc into user's manual and hacking manual, document much more |