Skip to content
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

8352620: C2: rename MemNode::memory_type() to MemNode::value_basic_type() #24427

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

sarannat
Copy link
Contributor

@sarannat sarannat commented Apr 3, 2025

Description: The current name MemNode::memory_type() is misleading because the returned type is a property of the value that is loaded/stored, not the memory that is accessed. Usually, the two of them match, but for mismatched memory accesses (arising e.g. from using Unsafe or memory segments) they might differ, e.g. one might store a value of type 'short' into an array of elements of type 'long'. The proposal was to rename MemNode::memory_type() to MemNode::value_basic_type() to clarify these cases.

Solution: Replaced all occurrence of MemNode::memory_type() with MemNode::value_basic_type()


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8352620: C2: rename MemNode::memory_type() to MemNode::value_basic_type() (Enhancement - P4)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24427/head:pull/24427
$ git checkout pull/24427

Update a local copy of the PR:
$ git checkout pull/24427
$ git pull https://git.openjdk.org/jdk.git pull/24427/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 24427

View PR using the GUI difftool:
$ git pr show -t 24427

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24427.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Apr 3, 2025

👋 Welcome back sarannat! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Apr 3, 2025

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

@openjdk
Copy link

openjdk bot commented Apr 3, 2025

@sarannat The following label will be automatically applied to this pull request:

  • hotspot-compiler

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added the hotspot-compiler hotspot-compiler-dev@openjdk.org label Apr 3, 2025
@sarannat sarannat marked this pull request as ready for review April 11, 2025 08:25
@openjdk openjdk bot added the rfr Pull request is ready for review label Apr 11, 2025
@mlbridge
Copy link

mlbridge bot commented Apr 11, 2025

Webrevs

@@ -2819,14 +2819,13 @@ int ConnectionGraph::find_init_values_null(JavaObjectNode* pta, PhaseValues* pha
offsets_worklist.append(offset);
Node* value = nullptr;
if (ini != nullptr) {
// StoreP::memory_type() == T_ADDRESS
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The value of this comment is debatable, but I think it is best to not remove it in this RFE (just rename memory_type to value_basic_type), to preserve the original scope of the RFE.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hotspot-compiler hotspot-compiler-dev@openjdk.org rfr Pull request is ready for review
Development

Successfully merging this pull request may close these issues.

2 participants