From: groepaz (groepaz_at_gmx.net)
Date: 2001-08-02 23:03:14
Hello Ullrich,
UvB> Yes, passing the problem to the emulator people would be an idea:-)
*LOL*
hehe, na i'd usually expect that job to be done by the debugger... the
more information available to the debugger, the better. it will also
make it easier to debug C code that has been optimized by the
compiler.
UvB> There is no special hook for this, but I don't think that you need such a
UvB> hook. Nothing prevents you from creating a profiling library and link against
UvB> it.
uh?!
i ment sth that would allow me to include a call to some of my
profiling functions automatically at the start and at the end of every
function. (the compiler would also need to pass function-name and
sourcefile-name to that function to make decent profiling possible).
myfunc(){
__prfstart("myfunc","main.c");
/* do sth */
__prfstop();
}
maybe smarter incase of the c64, (to save space in the binary) call
each function via some wrapper function, which again calls the profile
stuff and the actual function itself...like:
__prf(*fname,*file,*func,...){
__prfstart(fname,file);
__call(func,func++);
__prfstop();
}
main(){
__prf("myfunc","main.c",myfunc());
}
ofcoz i can do that manually for each function i want to analyze, but
thats a) pretty annoying and b) almost impossible to maintain on a
larger project (and only in larger projects that kinda profiling makes
sence anyway ;=))
--
Best regards,
groepaz mailto:groepaz_at_gmx.net
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo_at_musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.
This archive was generated by hypermail 2.1.3 : 2001-12-14 22:05:40 CET