Introduce the Function Isolation Pass
This commit introduces the Function Isolation Pass. We use the information provided by the Function Boundaries Detection Pass to organize the code that `revamb` places inside the `root` function in different LLVM functions. To do this we obviously need to introduce some changes and tricks to handle the execution of the translated program. The main idea is to have two different realms (one where the isolated functions live, one in which we have basically the old root function). We start the execution from the realm of the *non isolated* functions, and we transfer, as soon as possible, the execution to the *isolated functions* realm. We then have a fallback mechanism to restore the execution in the right place in the *non isolated* functions realm, and so on. The largest change, besides the re-organization of the code in different functions, is the use of the exception handling mechanism provided by the LLVM framework in order to be able to manage the switch between the two realms. We also introduce the `support.h` header file, which contains a couple of definitions used by `support.c` and that need to be shared with some of the components involved in the translation process. We have defined some helper functions, directly in C, that we use both for handling the exception mechanism and for giving extra debug informations when an exception is raised. The `revamb-dump` utility now supports the `-i` option to specify the path were to save the new LLVM module. The `translate` utility now supports the `-i` option that produces a binary in which the function isolation has been applied. We also introduced some tests that apply the function isolation pass to the `Runtime/` tests already present. In this way we can verify that the translation and the following function isolation preserve the behavior of the program. When serializing the new LLVM module we regenerate the metadata used for debug purposes, and for doing this, since we not longer have only the `root` function, we have changed some details in the `DebugHelper` class in order to be able to emit the metadata for all the functions of our interest in a single shot.
Showing
- CMakeLists.txt 4 additions, 2 deletionsCMakeLists.txt
- codegenerator.cpp 0 additions, 2 deletionscodegenerator.cpp
- debughelper.cpp 65 additions, 51 deletionsdebughelper.cpp
- debughelper.h 2 additions, 11 deletionsdebughelper.h
- docs/GeneratedIRReference.rst 132 additions, 1 deletiondocs/GeneratedIRReference.rst
- docs/RevambDumpUsage.rst 3 additions, 0 deletionsdocs/RevambDumpUsage.rst
- docs/TranslateUsage.rst 2 additions, 0 deletionsdocs/TranslateUsage.rst
- dump.cpp 33 additions, 0 deletionsdump.cpp
- functionboundariesdetection.cpp 3 additions, 3 deletionsfunctionboundariesdetection.cpp
- isolatefunctions.cpp 984 additions, 0 deletionsisolatefunctions.cpp
- isolatefunctions.h 37 additions, 0 deletionsisolatefunctions.h
- support.c 76 additions, 0 deletionssupport.c
- support.h 22 additions, 0 deletionssupport.h
- tests/Runtime/RuntimeTests.cmake 50 additions, 0 deletionstests/Runtime/RuntimeTests.cmake
- translate 32 additions, 13 deletionstranslate
Loading
Please register or sign in to comment