Re: Argument passing conventions and optimization

> I think you need to look for non-C compilers for this? If a compiler
> encounters a C function, it can't be sure it is not exported via a
> header somewhere, and those headers expect standard C calling
> conventions.


Most C compiler try following the standard ABI specifications of the
target processor. Now, if a compiler optimizes the function call
conventions, its not going to be sure if the callee is a library
function. So, its better to follow the starndard conventions.


Does this case even apply to parameter passing in the case of static
functions (in C)? Logically, we can perform optimization, but I am not
sure what kind of side effects this causes... The same can be the case
with functions calling other functions within the same C++ Namespace.


There could be a scenario where this kind of optimization can be
entrusted to the linker, but I guess its going to be a costly
stuff. Any thoughts...?


Regards,
Pradeep Tumati

Return to the comp.compilers page.
Search the comp.compilers archives again.