Hi! I've a particular module within a large project in which I wish to avoid making jumps to code segments from other modules (including C51 library code). Is there a means by which I can ensure that the compilation of this module will expand any calls to external code segments 'in-line'? I guess this is more-or-less what happens when optimising for speed, but would appreciate any feedback. (i.e is there a #pragma directive for speed?) Thanks! David
Okay. The lib. functions that my 'c' module require are LSTIDATA ,LLDIDATA and similar, they aren't inlined when the CODE(SPEED) option is specified. I guess my only means of inlining these is to do it manually. Thanks for your comments. David
Those routines are helper routines and they are not included inline. Refer to http://www.keil.com/support/docs/1964.htm for a little more information about what the routines do and how to "decode" the function names. Jon