| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
🤖 New build scheduled with the buildbot fleet by @brandtbucher for commit 867a686 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F136766%2Fmerge If you want to schedule another build, you need to add the 🔨 test-with-buildbots label again. |
Sorry, something went wrong.
|
!buildbot aarch64 RHEL8 LTO |
Sorry, something went wrong.
|
🤖 New build scheduled with the buildbot fleet by @brandtbucher for commit 7c9c3ff 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F136766%2Fmerge The command will test the builders whose names match following regular expression: aarch64 RHEL8 LTO The builders matched are:
|
Sorry, something went wrong.
| class TestJITStencils(unittest.TestCase): | ||
|
|
||
| def _build_jit_stencils(self, target: str) -> str: | ||
| with tempfile.TemporaryDirectory() as work: |
There was a problem hiding this comment.
I think os_helper.temp_dir is a bit more common in tests but either is fine :)
Sorry, something went wrong.
There was a problem hiding this comment.
Hm, I'll take a look!
Sorry, something went wrong.
There was a problem hiding this comment.
Is it, like, better? Haha.
Sorry, something went wrong.
There was a problem hiding this comment.
Couldn't tell you 😅 but it seems quite common. Though both are used so it probably doesn't matter :)
Sorry, something went wrong.
| parser.add_argument( | ||
| "-i", | ||
| "--input-file", | ||
| help="where to find the generated executor cases", |
There was a problem hiding this comment.
Do you think it's worth calling out that this is used to pass in the dummy file in our tests and/or that this could be useful for custom builds/debugging? Maybe not in help text but in a comment?
Sorry, something went wrong.
There was a problem hiding this comment.
I think I left a similar comment at the top of the PR. Is this the case of regenerating the file while in development so then be able to pass it?
Sorry, something went wrong.
There was a problem hiding this comment.
This is not fully related to this PR but sometime I change this line https://github.com/python/cpython/pull/136766/files#diff-700c6057d24addce74e8787edb5f5556f718299f6ef1742cbb1d79580cdb535cR199 and add delete=False because I want to inspect the temporary files that have been generated.
Do you think that we should expose this to the user (it would be useful for me)?
Sorry, something went wrong.
| pyconfig_h = pathlib.Path(sysconfig.get_config_h_filename()).resolve() | ||
| result, args = test.support.script_helper.run_python_until_end( | ||
| _TOOLS_JIT_BUILD_PY, | ||
| "--input-file", _TOOLS_JIT_TEST_TEST_EXECUTOR_CASES_C_H, |
There was a problem hiding this comment.
This is just for my understanding. is this needed in case we need to regenerate this during development and we need to test it, right?
Sorry, something went wrong.
| HoleValue.JUMP_TARGET: "state->instruction_starts[instruction->jump_target]", | ||
| HoleValue.ERROR_TARGET: "state->instruction_starts[instruction->error_target]", | ||
| # These should all have raised an error if they were actually used: | ||
| # HoleValue.WRITABLE: "", |
There was a problem hiding this comment.
I'm not sure I fully understand this. Can you expland please?
Sorry, something went wrong.
| parser.add_argument( | ||
| "-i", | ||
| "--input-file", | ||
| help="where to find the generated executor cases", |
There was a problem hiding this comment.
I think I left a similar comment at the top of the PR. Is this the case of regenerating the file while in development so then be able to pass it?
Sorry, something went wrong.
It's not a hard push back, but shouldn't be these changes go to a separate PR? |
Sorry, something went wrong.
There was a problem hiding this comment.
Ah, just noticed this was still open and I don't see any reason why it wouldn't still be valuable! I think the main thing outstanding was Diego's comment (#136766 (comment)). Otherwise, I'd be happy with an additional comment about the --input-file being used for tests and merging main back in. @brandtbucher I know you're busy these days; do you need/want help carrying this over the line?
Sorry, something went wrong.
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This is overdue, but it's especially valuable now that we're doing more subtle transformations on the machine code at JIT build time. This has a number of benefits:
The new test is in Lib/test/test_jit_stencils.py. This test uses Tools/jit/test/test_executor_cases.c.h to generate a few small test stencils, and compares them to the expected output in the corresponding Tools/jit/test/test_jit_stencils-*.h file.
Most of the changes in Tools/jit/_targets.py are just cleanup to make the generated stencils simpler and more consistent, or to fix the writable-data bug I mentioned above.