-
Notifications
You must be signed in to change notification settings - Fork 737
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
Fix string literal conversion warnings in optimizer, p #18472
Conversation
fe0dd7a
to
4b306b6
Compare
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.
Although this is still in draft, I thought I would go ahead and review it, assuming that it won't need to have any significant changes.
Fix string literal conversion warnings in runtime/compiler/optimizer Signed-off-by: Dylan Tuttle <[email protected]>
Fix string literal conversion warnings in runtime/compiler/p Signed-off-by: Dylan Tuttle <[email protected]>
4b306b6
to
ec025b8
Compare
Jenkins test sanity all jdk8,jdk11,jdk17,jdk21 |
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.
Looks good. Thanks!
JDK 11 aarch64 Linux test failures appear to be due to issue #18436. I am just waiting on some internal test results before merging. |
Internal testing on various hardware and O/S combinations ran into some failures due to infrastructure issues, but there didn't seem to be any problems related to the changes from this pull request. Merging - at last! |
Work towards fixing AIX warnings about assigning string literals to non-const char pointers by adding 'const' qualifiers to some string variables and parameters (or worst case scenario, casting to (char *)) in optimizer and p.
This PR contributes to (but does not close) #14859
This PR depends on: