-
Notifications
You must be signed in to change notification settings - Fork 40
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
[Wisp] Adapt Thread.stackSize. #153
Comments
ZhaiMo15
added a commit
to kuaishou-syslab/dragonwell17
that referenced
this issue
Sep 15, 2023
Summary: Previously wisp uses 512k as the stack size and ignores Thread.stackSize. This PR will make wisp to use Thread.stackSize as its stack size. Test Plan: jtreg:com/jdk/alibaba/wisp2/ Reviewed-by: yulei Issue: dragonwell-project#153
ZhaiMo15
pushed a commit
to kuaishou-syslab/dragonwell17
that referenced
this issue
Sep 15, 2023
Summary: 1. Remove un-impletemented functions in OptoRuntime. Test Plan: jtreg:com/jdk/alibaba/wisp2/ Reviewed-by: yulei Issue: dragonwell-project#153
yuleil
pushed a commit
that referenced
this issue
Sep 15, 2023
Summary: Previously wisp uses 512k as the stack size and ignores Thread.stackSize. This PR will make wisp to use Thread.stackSize as its stack size. Test Plan: jtreg:com/jdk/alibaba/wisp2/ Reviewed-by: yulei Issue: #153
yuleil
pushed a commit
that referenced
this issue
Sep 15, 2023
Summary: 1. Remove un-impletemented functions in OptoRuntime. Test Plan: jtreg:com/jdk/alibaba/wisp2/ Reviewed-by: yulei Issue: #153
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary:
Previously wisp uses 512k as the stack size and ignores Thread.stackSize.
This PR will make wisp to use Thread.stackSize as its stack size.
Test Plan: jtreg:com/jdk/alibaba/wisp2/
Reviewed-by: yulei
The text was updated successfully, but these errors were encountered: