-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
GH-115802: Use the GHC calling convention in JIT code #118287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
bdf7dd8
Use GHC calling convention on i686 and x86_64
brandtbucher 07e95c4
Fix call to emit on 32-bit platforms
brandtbucher e3a5f8a
Comments and cleanup
brandtbucher 0311f2f
Is this really needed?
brandtbucher 89764fd
t
brandtbucher 76ec119
...guess so.
brandtbucher 159d318
Wording
brandtbucher da351a2
Merge branch 'main' into justin-ghccc
brandtbucher 0cb4b2d
Catch up with main
brandtbucher 66db030
jit_code_ghccc -> jit_side_entry
brandtbucher d03f227
Clarify a few comments
brandtbucher File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
#include "Python.h" | ||
|
||
#include "pycore_ceval.h" | ||
#include "pycore_frame.h" | ||
#include "pycore_jit.h" | ||
|
||
// This is where the calling convention changes, on platforms that require it. | ||
// The actual change is patched in while the JIT compiler is being built, in | ||
// Tools/jit/_targets.py. On other platforms, this function compiles to nothing. | ||
_Py_CODEUNIT * | ||
_ENTRY(_PyInterpreterFrame *frame, PyObject **stack_pointer, PyThreadState *tstate) | ||
{ | ||
// This is subtle. The actual trace will return to us once it exits, so we | ||
// need to make sure that we stay alive until then. If our trace side-exits | ||
// into another trace, and this trace is then invalidated, the code for | ||
// *this function* will be freed and we'll crash upon return: | ||
PyAPI_DATA(void) _JIT_EXECUTOR; | ||
PyObject *executor = (PyObject *)(uintptr_t)&_JIT_EXECUTOR; | ||
Py_INCREF(executor); | ||
// Note that this is *not* a tail call: | ||
PyAPI_DATA(void) _JIT_CONTINUE; | ||
_Py_CODEUNIT *target = ((jit_func)&_JIT_CONTINUE)(frame, stack_pointer, tstate); | ||
Py_SETREF(tstate->previous_executor, executor); | ||
return target; | ||
} |
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.
Uh oh!
There was an error while loading. Please reload this page.