Openresty v3.0 #46
Merged
Openresty v3.0 #46
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
Compile unpack
Specialize to the global environment
Update to latest changes in v2.1
These instructions are useful to support Intel Control-flow Enforcement Technology (CET), when JIT code is called through idirect jump. See `man gcc` "-fcf-protection" and https://www.felixcloutier.com/x86/endbr64
Add support for ENDBR instructions
v2.1 Update
Support for UTF-8
Import OpenXRay changes
Better support for Android & iOS
Support for PSP Vita
Android Build SH's
Small steviegt6 patches
Specialize to the global environment
Update v3.0
JIT recording semantics assumes FFI calls are leaf regarding the LuaJIT VM: if the execution exited Lua world through FFI machinery it is not re-entering Lua world again. However, there is a way to break this assumption via FFI: one can re-enter LuaJIT VM via Lua C API used within the particular C routine called via FFI. As a result the following host stack mix is created: | Lua-FFI -> C routine -> Lua-C API -> Lua VM This sort of re-entrancy is not supported by LuaJIT tracing compiler. @mraleph named such kind of the call stack an "FFI sandwich" in the tarantool/tarantool#4427. This changeset introduces the mechanism for Lua-C API callbacks similar to the one implemented for Lua-FFI: trace recording is aborted when the execution re-enters LuaJIT VM. If re-enter is detected while running the particular mcode, the runtime finishes its execution with EXIT_FAILURE code and calls panic routine prior to the exit. Co-authored-by: Vyacheslav Egorov <[email protected]> Co-authored-by: Sergey Ostanevich <[email protected]> Signed-off-by: Igor Munkin <[email protected]>
Imun/ffi sandwich
v2.1 update
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.
No description provided.