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

8286397: Address possibly lossy conversions in jdk.hotspot.agent #9280

Closed

Conversation

rjernst
Copy link
Contributor

@rjernst rjernst commented Jun 24, 2022

Applied required casts in jdk.hotspot.agent for the upcoming warning.
Verified by cherry-picking @asotona's patch.


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-8286397: Address possibly lossy conversions in jdk.hotspot.agent

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 9280

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

Using diff file

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

Applied required casts in jdk.hotspot.agent for the upcoming warning.
Verified by cherry-picking @asotona's patch.
@bridgekeeper
Copy link

bridgekeeper bot commented Jun 24, 2022

👋 Welcome back rjernst! 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 openjdk bot added the rfr Pull request is ready for review label Jun 24, 2022
@openjdk
Copy link

openjdk bot commented Jun 24, 2022

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

  • serviceability

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 serviceability serviceability-dev@openjdk.org label Jun 24, 2022
@mlbridge
Copy link

mlbridge bot commented Jun 24, 2022

Webrevs

@@ -537,7 +537,7 @@ private int calculateClassDumpRecordSize(Klass k) {
List<Field> instanceFields = new ArrayList<>();
Iterator<Field> itr = null;
// loader + signer + protectionDomain + 2 reserved + fieldSize + cpool entris number
size += OBJ_ID_SIZE * 5 + INT_SIZE + SHORT_SIZE;
size += (int) (OBJ_ID_SIZE * 5 + INT_SIZE + SHORT_SIZE);
Copy link
Contributor

Choose a reason for hiding this comment

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

Why are INT_SIZE and SHORT_SIZE longs? It seems that making them int (along with all the other related _SIZE fields) is the proper fix for this and the changes below.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

These come from ObjectHeap. I do agree it would be better to change these upstream (all the type sizes there are currently long), but that would be a much more invasive change. I'm happy to try that, but it looked like a can of worms.

Copy link
Contributor

Choose a reason for hiding this comment

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

Unfortunately that eventually leads to Type.getSize(), which returns a long. I don't think you can change it to return an int, because some types (nonscalar) could need a long to fit their size, so you do need an int cast some point later. Probably the cast should be in the following code since we know all of these fit an in int:

  public ObjectHeap(TypeDataBase db) throws WrongTypeException {
    // Get commonly used sizes of basic types
    oopSize     = VM.getVM().getOopSize();
    byteSize    = db.getJByteType().getSize();
    charSize    = db.getJCharType().getSize();
    booleanSize = db.getJBooleanType().getSize();
    intSize     = db.getJIntType().getSize();
    shortSize   = db.getJShortType().getSize();
    longSize    = db.getJLongType().getSize();
    floatSize   = db.getJFloatType().getSize();
    doubleSize  = db.getJDoubleType().getSize();
  }

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I pushed 8115af5 to do as you suggested. That cleaned up most of the casts in HeapHprofBinWriter.

Copy link
Contributor

@plummercj plummercj left a comment

Choose a reason for hiding this comment

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

I didn't realize changing the type to an int would allow for the removal of so many existing casts. Looks like a good cleanup to me.

@openjdk
Copy link

openjdk bot commented Jun 27, 2022

@rjernst 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:

8286397: Address possibly lossy conversions in jdk.hotspot.agent

Reviewed-by: cjplummer, chegar

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 60 new commits pushed to the master branch:

  • 0709a6a: 8284942: Proxy building can just iterate superinterfaces once
  • 2961b7e: 8285364: Remove REF_ enum for java.lang.ref.Reference
  • 167ce4d: 8289421: No-PCH build for Minimal VM was broken by JDK-8287001
  • 108cd69: 8283726: x86_64 intrinsics for compareUnsigned method in Integer and Long
  • b96ba19: 8289182: NMT: MemTracker::baseline should return void
  • 779b4e1: 8287001: Add warning message when fail to load hsdis libraries
  • 910053b: 8280235: Deprecated flag FlightRecorder missing from VMDeprecatedOptions test
  • 7b3bf97: 8289401: Add dump output to TestRawRSACipher.java
  • 86dc760: Merge
  • 1504804: 8289398: ProblemList jdk/jfr/api/consumer/recordingstream/TestOnEvent.java on linux-x64 again
  • ... and 50 more: https://git.openjdk.org/jdk/compare/a5c25d8837664f9a7302cdb84afd3916da533144...master

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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@plummercj, @ChrisHegarty) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Jun 27, 2022
Copy link
Member

@ChrisHegarty ChrisHegarty left a comment

Choose a reason for hiding this comment

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

LGTM.

@rjernst
Copy link
Contributor Author

rjernst commented Jun 29, 2022

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Jun 29, 2022
@openjdk
Copy link

openjdk bot commented Jun 29, 2022

@rjernst
Your change (at version 2ce155b) is now ready to be sponsored by a Committer.

@ChrisHegarty
Copy link
Member

/sponsor

@openjdk
Copy link

openjdk bot commented Jun 30, 2022

Going to push as commit 7b5bd25.
Since your change was applied there have been 71 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 Jun 30, 2022
@openjdk openjdk bot closed this Jun 30, 2022
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Jun 30, 2022
@openjdk
Copy link

openjdk bot commented Jun 30, 2022

@ChrisHegarty @rjernst Pushed as commit 7b5bd25.

💡 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
integrated Pull request has been integrated serviceability serviceability-dev@openjdk.org
Development

Successfully merging this pull request may close these issues.

3 participants