LLVM Loader PoC #109
Closed
LLVM Loader PoC #109
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
`[ -z "${CLANG_FORMAT+x}" ]` checks if CLANG_FORMAT is unset, but the
variable will be set even if `which` fails, so we have to check if it is
empty instead.
`MEMORYCHECK_SUPPRESSIONS_FILE` can only take a single path and treats the entire semicolon-separated string as such. To pass multiple files, one has to pass each of them in as an individual command option.
Fix clang-format fallback check in pre-commit hook
Fix paths for memcheck suppressions files
|
This should not be merged into the project, the updated version of the PoC can be found here: https://github.com/yashtazor/LLVM-Loader-POC I am leaving here the zip version: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Trying out a PoC for LLVM Loader.
Start (29th March)
So far, I've been able to extract the LLVM IR from the C code.
Update (1st April)
Currently, I've found a way to extract functions in LLVM bit code (.bc) format. We can even have this in human-readable form for interpretation purposes. If we can somehow utilize these extracted methods to extract the names, arguments and return types, PoC is almost done.
Another way is to expose the LLVM IR module in the C code itself and then pass it as parameters in various methods of LLVM API to do the extraction work for us or we can even do it manually by iterating through various blocks of the LLVM IR code. This option hasn't been explored as of now and I plan on doing it in coming days.
Finally, after extraction (introspection/reflection) is done, we can move on to working with Metacall and implementing it inside the core.
Type of change
Checklist: