Add support for loading binary translated DLLs in MinGW #137
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.
This is the initial support for loading binary translation DLLs on Windows. #136
The way it works now is that MachineOptions has settings related to MinGW compilation on Linux (or rather, non-windows) systems where there is an expectation that you have a compiler in PATH.
Constructing
options.mingw_options
will by default usex86_64-w64-mingw32-gcc
as compiler. It will by default produce a rvbintr-HASH.dll in the build folder when a new program is translated.Using this we can package them with the script programs, load them on-demand, and get a free ~15x increase in performance for the sandboxed code.