Dave2001 said:
Whoa!!! I somehow did it, but I'm not sure quite how yet... Here's some of the output (i didn't run anything when i used pj64)
I'll try to figure out what I did & post it here.
Func Func+Child Hit
Time % Time % Count Function
---------------------------------------------------------
0.000 0.0 0.000 0.0 1 CountCombine(void) (combine.obj)
0.000 0.0 0.000 0.0 1 INI_Close(void) (ini.obj)
0.000 0.0 0.000 0.0 1 INI_FindSection(char *) (ini.obj)
0.000 0.0 0.000 0.0 17 INI_GetInt(char *,int,int) (ini.obj)
0.000 0.0 0.000 0.0 1 INI_Open(void) (ini.obj)
0.000 0.0 0.000 0.0 1 _$E17 (main.obj)
0.000 0.0 0.000 0.0 1 _$E19 (main.obj)
0.000 0.0 0.000 0.0 1 _$E20 (main.obj)
0.000 0.0 0.000 0.0 2 _DllMain@12 (main.obj)
0.000 0.0 0.000 0.0 1 _GetDllInfo (main.obj)
0.000 0.0 0.000 0.0 1 _InitiateGFX (main.obj)
0.000 0.0 0.000 0.0 1 _ReadSettings (main.obj)
0.000 0.0 0.000 0.0 3 __mtlockinit (mtlock.obj)
...
That's function profiling.
It lists how many times your functions get called. It's useful to see if a function gets called lots, then you should try to optimize that function, and then you can see which functions that are NOT called. Those should be removed, saves you size
There's other profiling options as well, Dave. Try them, too.
Hacktarux: Profiling isn't hard at all to use. You just need to have an EXE to do it the easy way.
You simply goto options and select "enable profiling" in debug. Then goto build-->profile and you can select a method of profiling. When selected, click OK and the app will automaticlly compile and run. After it's done, you'll see the results of the profiling.