[Gllug] Compiling a Kernel

[Dave Jones]

On Sun, May 26, 2002 at 11:31:54PM +0100, Nix wrote:

 > (hacking up a little script to profile GCC with oprofile, test-coverage
 > analyze it with gcov and profile it with -pg in succession... about 140
 > hours for a single run, but this is what computer time is for,
 > surely... ;} )

Reminds me, gcc 3.1's optimiser now has profile driven feedback, which looks quite fun.
You compile with --profile-arcs, run the app, and then recompile with -fbranch-probabilities
Could prove to have interesting results for a lot of cpu-hogging apps,
though I've not seen any real-world results, and haven't had time to
play with it much yet.

Also, going off on a complete tangent, if you're a C/C++ programmer, and you
haven't seen valgrind yet, run (don't walk) to the homepage[1] immediately and
grab a copy.  It's like electric fence on steroids, and has turned up
lots of bugs in numerous bits of code I thought were completely problem free.

    Dave.

[1] http://developer.kde.org/~sewardj/

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs


-- 
Gllug mailing list  -  Gllug at linux.co.uk
http://list.ftech.net/mailman/listinfo/gllug