Function calling method, computing device and storage medium

Abstract

The invention discloses a function calling method, computing equipment and a storage medium, and the method comprises the steps: identifying each to-be-called function in a to-be-run program to generate a function signature sequence number table; modifying a calling instruction of each function to be called; generating a static function file based on the function signature sequence number table and compiling the static function file; and running the to-be-run program, and if function calling occurs during running, calling a corresponding function according to the function signature sequence number table and the modified calling instruction. According to the technical scheme, call agreement conversion between different architectures and platforms is completed through automatic construction and static function call, and function call with high efficiency and low overhead is achieved.

Description

technical field [0001] The invention relates to the technical field of computers, in particular to a function calling method, a computing device and a storage medium. Background technique [0002] The current mainstream cross-platform and cross-architecture function call scheme is realized by using the dynamic call method of dyncall (a dynamic call library). Specifically, manually fill in the specific function signature before calling, and through the identification and processing of the function signature, manually push the parameters to be processed to the internal virtual stack to achieve ABI (Application Binary Interface, application binary interface) conversion, and then run When parsing the corresponding parameters and type information, and passing in according to the function calling convention of the machine architecture, after the function is executed, the return value is obtained and returned according to the function signature. [0003] There are three major defe...

AI Technical Summary

Problems solved by technology

[0003] There are three major defects in the above scheme: (1) In the stage before compiling, there is a lot of work that needs to be sorted and packaged manually, and the function signature cannot be automatically recognized. When the code volume of the program is large and the number of functions is large, manual input The workload of processing and sorting is huge, and it is difficult to ensure the accuracy of large-scale operations; (2) The parsing process of the function signature is cumbersome and inefficient. Before running the function, the caller will parse the function signature and pass in the parameters in order , that is, every time a function call occurs in the program, there will be a process of parsing and passing parameters. When running a large-scale program with relatively high performance requirements such as a game, the performance decline is quite obvious, causing the program to run slowly and freeze. (3) When building the call stack, some additional overhead will be generated. For embedded devices with relatively short memory, it is easy to cause program crashes due to insufficient memory overhead, etc. fatal problem

Images