-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Add a white list of known non-safepoint functions #22709
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
Conversation
|
I should add that |
005a0a2 to
a66d522
Compare
|
So it turns out that the |
a66d522 to
ad8589a
Compare
|
@nanosoldier |
|
Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. cc @jrevels |
These are functions we emit in codegen directly that are known to not contain any safepoint
ad8589a to
fc31ce5
Compare
| end | ||
| @test pointer_not_safepoint() == 3 | ||
|
|
||
| # The current memcmp threshold is 512bytes, make sure this struct has the same size on |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would this silently test a different codepath then if that limit were adjusted?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No. that's what the @memcmp test below is for.
|
Travis linux 64 has a download issue. Restarted... |
These are functions we emit in codegen directly that are known to not contain any safepoint