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

Clean up deprecated recognized method inlining #2248

Merged
merged 1 commit into from
Jul 5, 2018

Conversation

0dvictor
Copy link
Contributor

@0dvictor 0dvictor commented Jun 21, 2018

Following 4 recognized methods have been long deprecated:

  1. com_ibm_jit_JITHelpers_hashCodeImpl
  2. java_lang_Object_hashCodeImpl
  3. java_lang_System_currentTimeMillis [X86 only]
  4. java_lang_Integer_rotateLeft [X86 only]
    Cleaning-up code related them.

Signed-off-by: Victor Ding dvictor@ca.ibm.com

@0dvictor 0dvictor changed the title Clean up deprecated recognized method inlining X86 Clean up deprecated recognized method inlining Jun 22, 2018
@0dvictor 0dvictor force-pushed the cleanup branch 2 times, most recently from 286838b to 00cbb56 Compare June 22, 2018 15:41
@andrewcraik
Copy link
Contributor

I'm having trouble following the logic for the currentTimeMillis removal - where is the point that makes it clearly dead?

@0dvictor
Copy link
Contributor Author

The code is not used under any scenarios and will crash JVM if it kicks in.

  1. The only path reaching inlineCurrentTimeMillis() is from VMinlineCallEvaluator(), which can only be reached from directCallEvaluator(). However, directCallEvaluator() does not route TR::java_lang_System_nanoTime to VMinlineCallEvaluator().
  2. inlineCurrentTimeMillis() uses the call node's first (and only) child as the address to hold temporary value; however, the child is actually FastJNI related. If it is inlineCurrentTimeMillis() kicks in, JVM may crash.

@andrewcraik
Copy link
Contributor

@0dvictor sorry I didn't get back to this one - can you rebase so I can run the build?

@0dvictor
Copy link
Contributor Author

Rebased.

@andrewcraik
Copy link
Contributor

Jenkins test sanity

@andrewcraik
Copy link
Contributor

Jenkins test sanity

Following 4 recognized methods have been long deprecated:
1. com_ibm_jit_JITHelpers_hashCodeImpl
2. java_lang_Object_hashCodeImpl
3. java_lang_System_currentTimeMillis [X86 only]
4. java_lang_Integer_rotateLeft       [X86 only]
Cleaning-up code related them.

Signed-off-by: Victor Ding <dvictor@ca.ibm.com>
@0dvictor
Copy link
Contributor Author

0dvictor commented Jul 4, 2018

There were Travis CI failures caused by out-of-dated OMR; hence I've rebased and re-launched Travis CI. All checks have passed now, could you re-launch sanity tests? @andrewcraik

@andrewcraik
Copy link
Contributor

Jenkins test sanity

@0dvictor
Copy link
Contributor Author

0dvictor commented Jul 5, 2018

Windows failures are due to #2129

Copy link
Contributor

@andrewcraik andrewcraik left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@andrewcraik andrewcraik left a comment

Choose a reason for hiding this comment

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

based on victor's comment and a review of the code this does look to be genuinely dead.

@andrewcraik andrewcraik merged commit c76c527 into eclipse-openj9:master Jul 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants