>> The correct function is selected by the compiler and the overhead >> is IMO in our area not an issue. > In embedded developpment, "IMO" can be argued to be not precise > enough.
Well, we talk about the PC-side of an embedded system. So we have more then enough horse power here. The overhead is: > On typical hardware, the machine-code is two 'load's plus a call: Take a look at: http://www.parashift.com/c++-faq-lite/virtual-functions.html#faq-20.4 So this is defently not an issue. > But then, QT and KDE do not have a requirement to "communicate with > CPUs for embedded debugging purposes, including watching them > running, on a not-so-fast serial link". The "not-so-fast serial link" is the issue here. If the data comes slow, the CPU is 95% idle. Best Regards, Carsten _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
