Fix comparison of non-pointer to NULL #18266
Merged
Conversation
This file contains 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
Fix plinux warning concerning a comparison of a non-pointer to NULL by replacing the NULL with 0 Signed-off-by: Dylan Tuttle <[email protected]>
|
Jenkins test sanity plinux,aix jdk17,jdk21 |
|
Failures are expected CRIU test failures. The change is very straightforward and safe, so merging. |
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.
Fix plinux warning concerning a comparison of a non-pointer to NULL by replacing the NULL with 0.
getHeapBase()returns a value of typeintptr_t, which is an integer value and therefore can not be NULL. Since the variable being returned,_heapBase, it is initialized to 0 in omr/compiler/control/OMROptions.hpp, it seems sensible to compare its value to 0 instead of NULL.This PR contributes to (but does not close) #14859