This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: standard calling convention for static function


On 12/04/2017 03:47 PM, David Brown wrote:
On 04/12/17 14:20, David Livshin wrote:

Hello,

How to force gcc to conform to it standard calling convention while
compiling static function?


What are you trying to do here?  I'd imagine that any use of a static
function which /required/ standard calling conventions would ensure that
the function is generated as a normal stand-alone function (such as if
you pass its address to other code for use as a callback).  It is only
if the compiler knows all use of the function that it can do inlining,
partial inlining, or other "non-standard" manipulation.




I am processing compiler-generated assembly code; not knowing calling convention utilized makes it difficult.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]