Skip to content

Conversation

@iklam
Copy link
Member

@iklam iklam commented Jul 2, 2025

A module has both a Java and a C++ representation

  • C++: ModuleEntry
  • Java: java.lang.Module

In C++, we have the following two methods

  • ModuleEntry* InstanceKlass::module()
  • oop ModuleEntry::module()

This can lead to confusing code like this:

InstanceKlass* ik = ...;
oop module = ik->module()->module()

Proposal:

  • Leave InstanceKlass::module() as is -- there's another function with the same style: PackageEntry* InstanceKlass::package()
  • Rename ModuleEntry::module() to ModuleEntry::module_oop(), so the above example can be more readable:
InstanceKlass* ik = ...;
oop module = ik->module()->module_oop()

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-8361292: Rename ModuleEntry::module() to module_oop() (Enhancement - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 26102

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Jul 2, 2025

👋 Welcome back iklam! 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 Jul 2, 2025

@iklam This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8361292: Rename ModuleEntry::module() to module_oop()

Reviewed-by: coleenp, ccheung, sspitsyn

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 3 new commits pushed to the master branch:

  • 74822ce: 8358183: [JVMCI] crash accessing nmethod::jvmci_name in CodeCache::aggregate
  • ea86a20: 8357424: [JVMCI] Avoid incrementing decompilation count for hosted compiled nmethod
  • 5e30bf6: 8360116: Add support for AVX10 floating point minmax instruction

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

@openjdk openjdk bot added the rfr Pull request is ready for review label Jul 2, 2025
@openjdk
Copy link

openjdk bot commented Jul 2, 2025

@iklam The following labels will be automatically applied to this pull request:

  • graal
  • hotspot
  • serviceability

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

@openjdk openjdk bot added graal graal-dev@openjdk.org serviceability serviceability-dev@openjdk.org hotspot hotspot-dev@openjdk.org labels Jul 2, 2025
@mlbridge
Copy link

mlbridge bot commented Jul 2, 2025

Webrevs

Copy link
Contributor

@coleenp coleenp left a comment

Choose a reason for hiding this comment

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

I like this change other than precond(). ModuleEntry vs java.lang.Module oops is clearer with a different method name. I've been confused by this too.

assert(jlm != nullptr, "Null jlm in module_to ModuleEntry");
intptr_t identity_hash = jlm->identity_hash();
oop module_oop = module_to->module_oop();
precond(module_oop != nullptr);
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't like precond() when you could have a useful assert message instead.

assert(jlm != nullptr, "Null jlm in module_from ModuleEntry");
intptr_t identity_hash = jlm->identity_hash();
oop module_oop = module_from->module_oop();
precond(module_oop != nullptr);
Copy link
Contributor

Choose a reason for hiding this comment

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

same here. "Module oop should be non-null in ModuleEntry"

Copy link
Member Author

Choose a reason for hiding this comment

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

We have just read the oop from the module entry and assert that it's not null, so the original message didn't add any extra information. That's why I removed it.

I have added back a message, "should have been initialized".

The real story is more complex, but I think this message willl give enough hints -- the module oop is usually initialized inside the ModuleEntry constructor, except for a few cases for the java.base module where the module oop is retroactively updated. In any case, by the time we reach this assert, the module oop must have been initialized in one of those possible paths.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Jul 2, 2025
@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Jul 2, 2025
@openjdk openjdk bot added the ready Pull request is ready to be integrated label Jul 2, 2025
Copy link
Member

@calvinccheung calvinccheung left a comment

Choose a reason for hiding this comment

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

Looks good.

ModuleEntry* ModuleEntryTable::_javabase_module = nullptr;

oop ModuleEntry::module() const { return _module.resolve(); }
oop ModuleEntry::module_oop() const { return _module_handle.resolve(); }
Copy link
Member

Choose a reason for hiding this comment

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

(Pre-existing) Just wondering why this one-liner function doesn't reside in the moduleEntry.hpp?

Copy link
Member Author

Choose a reason for hiding this comment

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

I think it's because OopHandle::resolve() is an inline function, but we are not allowed to include xxx.inline.hpp in non-inlined .hpp files.

Copy link
Contributor

@sspitsyn sspitsyn left a comment

Choose a reason for hiding this comment

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

Looks good.

@iklam
Copy link
Member Author

iklam commented Jul 3, 2025

Thanks @coleenp @calvinccheung @sspitsyn for the review
/integrate

@openjdk
Copy link

openjdk bot commented Jul 3, 2025

Going to push as commit 66836d4.
Since your change was applied there have been 13 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Jul 3, 2025
@openjdk openjdk bot closed this Jul 3, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Jul 3, 2025
@openjdk
Copy link

openjdk bot commented Jul 3, 2025

@iklam Pushed as commit 66836d4.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

graal graal-dev@openjdk.org hotspot hotspot-dev@openjdk.org integrated Pull request has been integrated serviceability serviceability-dev@openjdk.org

Development

Successfully merging this pull request may close these issues.

4 participants