-
Notifications
You must be signed in to change notification settings - Fork 13
Add UJIT.reset_stats! #62
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
Conversation
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
To allow analyzing sections of the application.
maximecb
approved these changes
Mar 3, 2021
tenderlove
pushed a commit
that referenced
this pull request
May 18, 2021
GitHub: fix GH-62 Reported by Cody Krieger. Thanks!!! ruby/fiddle@284b820f2d
tenderlove
pushed a commit
that referenced
this pull request
Jun 21, 2021
Two JITs running at once may result in strange interactions. Lets disable YJIT while running the MJIT tests.
maximecb
pushed a commit
that referenced
this pull request
Oct 19, 2021
Two JITs running at once may result in strange interactions. Lets disable YJIT while running the MJIT tests.
maximecb
pushed a commit
that referenced
this pull request
Oct 19, 2021
This reverts commit 60f3f25. We don't need to pass --disable-yjit when running MJIT tests anymore because we are off by default.
noahgibbs
pushed a commit
that referenced
this pull request
Oct 20, 2021
Two JITs running at once may result in strange interactions. Lets disable YJIT while running the MJIT tests.
noahgibbs
pushed a commit
that referenced
this pull request
Oct 20, 2021
This reverts commit 60f3f25. We don't need to pass --disable-yjit when running MJIT tests anymore because we are off by default.
XrXr
pushed a commit
that referenced
this pull request
Oct 20, 2021
Two JITs running at once may result in strange interactions. Lets disable YJIT while running the MJIT tests.
XrXr
added a commit
that referenced
this pull request
Oct 20, 2021
This reverts commit 60f3f25. We don't need to pass --disable-yjit when running MJIT tests anymore because we are off by default.
XrXr
pushed a commit
that referenced
this pull request
Oct 20, 2021
Two JITs running at once may result in strange interactions. Lets disable YJIT while running the MJIT tests.
XrXr
added a commit
that referenced
this pull request
Oct 20, 2021
This reverts commit 60f3f25. We don't need to pass --disable-yjit when running MJIT tests anymore because we are off by default.
XrXr
pushed a commit
that referenced
this pull request
Oct 21, 2021
Two JITs running at once may result in strange interactions. Lets disable YJIT while running the MJIT tests.
XrXr
added a commit
that referenced
this pull request
Oct 21, 2021
This reverts commit 60f3f25. We don't need to pass --disable-yjit when running MJIT tests anymore because we are off by default.
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.
To allow analyzing sections of the application.
Usage in railsbench: ruby/ruby-bench#2
Doesn't change the side exit stats much, but gives a better idea for how many iseqs compile.