Are there any performance penalities for using XFLAT accesor functions?
As described above, the xflat-gcc tool inserts calls to data accessor functions to manage access to global variables across such module boundaries. Typical dereferencing in this manner should not cause an measurable performance degradation if it is infrequent. However, such dereferencing could be a performance issue if such a variable is referenced at a high duty, say, in a “tight” loop. Then the small amount of processing required to access the variable could become a performance issue. In this case, you might want to save a pointer to the variable reference so that you do not call the accessor function at a high rate.
Related Questions
- May an employer apply the same quantitative and qualitative requirements for performance of essential functions to an employee with a disability that it applies to employees without disabilities?
- What type of performance management functions does Metro Ethernet Manager support?
- What are the functions of the radiator overflow tank in a ford explorer?
