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

From: David Brown <david at westcontrol dot com>
To: David Livshin <david dot livshin at dalsoft dot com>, <gcc-help at gcc dot gnu dot org>
Date: Mon, 4 Dec 2017 15:17:54 +0100
Subject: Re: standard calling convention for static function
Authentication-results: sourceware.org; auth=none
References: <bf6a904e-9f34-1bd8-61fa-50ae705543af@dalsoft.com> <5A2551DD.8050902@westcontrol.com> <e1535ff3-e2f3-c4ce-caa2-0d9f232aa2ec@dalsoft.com>

On 04/12/17 14:55, David Livshin wrote:
> 
> I am processing compiler-generated assembly code; not knowing calling
> convention utilized makes it difficult.

Why are you wanting to make the functions static?  Just use external
linkage, and the functions will be generated for use from external code.

You can also use the "-fkeep-static-functions" compiler flag.  I am not
sure that it /guarantees/ you will get standard calling conventions, but
I'd be surprised if you got something else.

Follow-Ups:
- Re: standard calling convention for static function
  - From: David Livshin

References:
- standard calling convention for static function
  - From: David Livshin
- Re: standard calling convention for static function
  - From: David Brown
- Re: standard calling convention for static function
  - From: David Livshin

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