8000 YJIT: reduce default exec mem size to 48MiB by maximecb · Pull Request #9685 · ruby/ruby · GitHub
[go: up one dir, main page]

Skip to content

YJIT: reduce default exec mem size to 48MiB #9685

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 1 commit into from
Jan 24, 2024

Conversation

maximecb
Copy link
Contributor

Based on user feedback from @jhawthorn and others. Better for small and memory-constrained deployments.

NOTE: This commit should be included in the next Ruby 3.3.x point release. @XrXr should we tag someone specific?

Based on user feedback from @jhawthorn and others.
Better for small and memory-constrained deployments.

NOTE: This commit should be included in the next Ruby 3.3.x point
release. @XrXr should we tag someone specific?
@maximecb maximecb changed the title YJIT: reduce default exec mem size to 48MiB based YJIT: reduce default exec mem size to 48MiB Jan 24, 2024
@matzbot matzbot requested a review from a team January 24, 2024 17:43
@XrXr
Copy link
Member
XrXr commented Jan 24, 2024

To follow the usual workflow, I think you need to have a closed ticket on https://bugs.ruby-lang.org/ and tag it with this commit by mentioning the ticket number in the message, like [Bug #XXXX]. Otherwise you could make a PR against the branch.

@maximecb
Copy link
Contributor Author

@XrXr what is the branch?

@maximecb maximecb enabled auto-merge (squash) January 24, 2024 18:14
@maximecb maximecb merged commit 1702528 into ruby:master Jan 24, 2024
@maximecb maximecb deleted the yjit_smol_exec_mem branch January 24, 2024 18:14
@k0kubun
Copy link
Member
k0kubun commented Jan 24, 2024

a small fix: #9687

@k0kubun
Copy link
Member
k0kubun commented Jan 24, 2024

what is the branch?

It's ruby_3_3 branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0