Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

GH-126892: Reset warmup counters when JIT compiling code#126893

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
brandtbucher merged 6 commits intopython:mainfrombrandtbucher:reset-counters
Nov 20, 2024
Merged
Changes from1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
PrevPrevious commit
NextNext commit
Disable the JIT during strace
  • Loading branch information
@brandtbucher
brandtbucher committedNov 19, 2024
commita6e173f7adf6c88cc3a94e0a31f56ca5706d2ff0
5 changes: 4 additions & 1 deletionLib/test/support/strace_helper.py
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -91,7 +91,10 @@ def _make_error(reason, details):
res, cmd_line = run_python_until_end(
"-c",
textwrap.dedent(code),
__run_using_command=[_strace_binary] + strace_flags)
__run_using_command=[_strace_binary] + strace_flags,
# Don't want to trace our JIT's own mmap and mprotect calls:
PYTHON_JIT="0",
Copy link
Contributor

@cmaloneycmaloneyNov 20, 2024
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Guessing this showed up in thetest_fileio testtest_syscalls_read?

I have been keeping an eye on / working through a couple other issues where mmap(NULL) and mprotect show up, trying to figure out if just excluding those two from that test would be good/effective (memory allocation happening in reading files is fine / not what the test is focused on).

Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Yeah, I was wondering if this was susceptible to catching badly-timed arena allocations and such too. Might make sense to have an option to ignore themmap/munmap/mprotect family of functions instead of this ad-hoc fix.

I'm just not familiar with how this is being used, and didn't want to change the meaning/behavior of the tests too dramatically.

cmaloney reacted with thumbs up emoji
)
except OSError as err:
return _make_error("Caught OSError", err)

Expand Down
Loading

[8]ページ先頭

©2009-2025 Movatter.jp