Java Object.hashCode()返回的是对象内存地址?

本文详细剖析了Java中Object.hashCode()方法的实现原理,揭示了OpenJDK8中hashCode的计算并非基于对象内存地址,而是采用Marsaglia's xorshift scheme随机数算法结合线程状态生成随机数。

Java Object.hashCode()返回的是对象内存地址?

阅读 2060
收藏 29
2017-07-14
原文链接: www.jianshu.com

基于OpenJDK 8

一直以为Java Object.hashCode()的结果就是通过对象的内存地址做相关运算得到的,但是无意在网上看到有相应的意见争论,故抽时间从源码层面验证了剖析了hashCode的默认计算方法。

先说结论:OpenJDK8 默认hashCode的计算方法是通过和当前线程有关的一个随机数+三个确定值,运用Marsaglia's xorshift scheme随机数算法得到的一个随机数。和对象内存地址无关。

下面通过查找和分析OpenJDK8源码实现来一步步分析。

1. 查找java.lang.Object.hashCode()源码

public native int hashCode();

2. 导出Object的JNI头文件

切换到Object.class文件所在目录,执行 javah -jni java.lang.Object,得到java_lang_Object.h文件,文件内容如下:

/* DO NOT EDIT THIS FILE - it is machine generated */
#include <jni.h>
/* Header for class java_lang_Object */

#ifndef _Included_java_lang_Object
#define _Included_java_lang_Object
#ifdef __cplusplus
extern “C” {
#endif
/*

  • Class: java_lang_Object
  • Method: registerNatives
  • Signature: ()V
    /
    JNIEXPORT void JNICALL Java_java_lang_Object_registerNatives
    (JNIEnv
    , jclass);

    /*
  • Class: java_lang_Object
  • Method: getClass
  • Signature: ()Ljava/lang/Class;
    /
    JNIEXPORT jclass JNICALL Java_java_lang_Object_getClass
    (JNIEnv
    , jobject);

    /*
  • Class: java_lang_Object
  • Method: hashCode
  • Signature: ()I
    /
    JNIEXPORT jint JNICALL Java_java_lang_Object_hashCode
    (JNIEnv
    , jobject);

    /*
  • Class: java_lang_Object
  • Method: clone
  • Signature: ()Ljava/lang/Object;
    /
    JNIEXPORT jobject JNICALL Java_java_lang_Object_clone
    (JNIEnv
    , jobject);

    /*
  • Class: java_lang_Object
  • Method: notify
  • Signature: ()V
    /
    JNIEXPORT void JNICALL Java_java_lang_Object_notify
    (JNIEnv
    , jobject);

    /*
  • Class: java_lang_Object
  • Method: notifyAll
  • Signature: ()V
    /
    JNIEXPORT void JNICALL Java_java_lang_Object_notifyAll
    (JNIEnv
    , jobject);

    /*
  • Class: java_lang_Object
  • Method: wait
  • Signature: (J)V
    /
    JNIEXPORT void JNICALL Java_java_lang_Object_wait
    (JNIEnv
    , jobject, jlong);

    #ifdef __cplusplus
    }
    #endif
    #endif

    3 . 查看Object的native方法实现


    OpenJDK源码链接:hg.openjdk.java.net/jdk8u/jdk8u… ,查看Object.c文件,可以看到hashCode()的方法被注册成由JVM_IHashCode方法指针来处理。

    static JNINativeMethod methods[] = {
    {“hashCode”, “()I”, (void *)&JVM_IHashCode},//hashcode的方法指针JVM_IHashCode
    {“wait”, “(J)V”, (void *)&JVM_MonitorWait},
    {“notify”, “()V”, (void *)&JVM_MonitorNotify},
    {“notifyAll”, “()V”, (void *)&JVM_MonitorNotifyAll},
    {“clone”, “()Ljava/lang/Object;”, (void )&JVM_Clone},
    };

    而JVM_IHashCode方法指针在 openjdk\hotspot\src\share\vm\prims\jvm.cpp中定义为:

    JVM_ENTRY(jint, JVM_IHashCode(JNIEnv env, jobject handle))
    JVMWrapper(“JVM_IHashCode”);
    // as implemented in the classic virtual machine; return 0 if object is NULL
    return handle == NULL ? 0 : ObjectSynchronizer::FastHashCode (THREAD, JNIHandles::resolve_non_null(handle)) ;
    JVM_END

    从而得知,真正计算获得hashCode的值是ObjectSynchronizer::FastHashCode


    4 . ObjectSynchronizer::fashHashCode方法的实现


    openjdk\hotspot\src\share\vm\runtime\synchronizer.cpp 找到其实现方法。

    intptr_t ObjectSynchronizer::FastHashCode (Thread * Self, oop obj) {
    if (UseBiasedLocking) {
    // NOTE: many places throughout the JVM do not expect a safepoint
    // to be taken here, in particular most operations on perm gen
    // objects. However, we only ever bias Java instances and all of
    // the call sites of identity_hash that might revoke biases have
    // been checked to make sure they can handle a safepoint. The
    // added check of the bias pattern is to avoid useless calls to
    // thread-local storage.
    if (obj->mark()->has_bias_pattern()) {
    // Box and unbox the raw reference just in case we cause a STW safepoint.
    Handle hobj (Self, obj) ;
    // Relaxing assertion for bug 6320749.
    assert (Universe::verify_in_progress() ||
    !SafepointSynchronize::is_at_safepoint(),
    “biases should not be seen by VM thread here”);
    BiasedLocking::revoke_and_rebias(hobj, false, JavaThread::current());
    obj = hobj() ;
    assert(!obj->mark()->has_bias_pattern(), “biases should be revoked by now”);
    }
    }

// hashCode() is a heap mutator …
// Relaxing assertion for bug 6320749.
assert (Universe::verify_in_progress() ||
!SafepointSynchronize::is_at_safepoint(), “invariant”) ;
assert (Universe::verify_in_progress() ||
Self->is_Java_thread() , “invariant”) ;
assert (Universe::verify_in_progress() ||
((JavaThread *)Self)->thread_state() != _thread_blocked, “invariant”) ;

ObjectMonitor* monitor = NULL;
markOop temp, test;
intptr_t hash;
markOop mark = ReadStableMark (obj);

// object should remain ineligible for biased locking
assert (!mark->has_bias_pattern(), “invariant”) ;

if (mark->is_neutral()) {
hash = mark->hash(); // this is a normal header
if (hash) { // if it has hash, just return it
return hash;
}
hash = get_next_hash(Self, obj); // allocate a new hash code
temp = mark->copy_set_hash(hash); // merge the hash code into header
// use (machine word version) atomic operation to install the hash
test = (markOop) Atomic::cmpxchg_ptr(temp, obj->mark_addr(), mark);
if (test == mark) {
return hash;
}
// If atomic operation failed, we must inflate the header
// into heavy weight monitor. We could add more code here
// for fast path, but it does not worth the complexity.
} else if (mark->has_monitor()) {
monitor = mark->monitor();
temp = monitor->header();
assert (temp->is_neutral(), “invariant”) ;
hash = temp->hash();
if (hash) {
return hash;
}
// Skip to the following code to reduce code size
} else if (Self->is_lock_owned((address)mark->locker())) {
temp = mark->displaced_mark_helper(); // this is a lightweight monitor owned
assert (temp->is_neutral(), “invariant”) ;
hash = temp->hash(); // by current thread, check if the displaced
if (hash) { // header contains hash code
return hash;
}
// WARNING:
// The displaced header is strictly immutable.
// It can NOT be changed in ANY cases. So we have
// to inflate the header into heavyweight monitor
// even the current thread owns the lock. The reason
// is the BasicLock (stack slot) will be asynchronously
// read by other threads during the inflate() function.
// Any change to stack may not propagate to other threads
// correctly.
}

// Inflate the monitor to set hash code
monitor = ObjectSynchronizer::inflate(Self, obj);
// Load displaced header and check it has hash code
mark = monitor->header();
assert (mark->is_neutral(), “invariant”) ;
hash = mark->hash();
if (hash == 0) {
hash = get_next_hash(Self, obj);
temp = mark->copy_set_hash(hash); // merge hash code into header
assert (temp->is_neutral(), “invariant”) ;
test = (markOop) Atomic::cmpxchg_ptr(temp, monitor, mark);
if (test != mark) {
// The only update to the header in the monitor (outside GC)
// is install the hash code. If someone add new usage of
// displaced header, please update this code
hash = test->hash();
assert (test->is_neutral(), “invariant”) ;
assert (hash != 0, “Trivial unexpected object/monitor header usage.”);
}
}
// We finally get the hash
return hash;
}

该方法中

// Load displaced header and check it has hash code
mark = monitor->header();
assert (mark->is_neutral(), “invariant”) ;
hash = mark->hash();
if (hash == 0) {
hash = get_next_hash(Self, obj);

}

对hash值真正进行了计算,查看get_next_hash方法源码hg.openjdk.java.net/jdk8u/jdk8u…

static inline intptr_t get_next_hash(Thread * Self, oop obj) {
intptr_t value = 0 ;
if (hashCode == 0) {
// This form uses an unguarded global Park-Miller RNG,
// so it’s possible for two threads to race and generate the same RNG.
// On MP system we’ll have lots of RW access to a global, so the
// mechanism induces lots of coherency traffic.
value = os::random() ;
} else
if (hashCode == 1) {
// This variation has the property of being stable (idempotent)
// between STW operations. This can be useful in some of the 1-0
// synchronization schemes.
intptr_t addrBits = cast_from_oop<intptr_t>(obj) >> 3 ;
value = addrBits ^ (addrBits >> 5) ^ GVars.stwRandom ;
} else
if (hashCode == 2) {
value = 1 ; // for sensitivity testing
} else
if (hashCode == 3) {
value = ++GVars.hcSequence ;
} else
if (hashCode == 4) {
value = cast_from_oop<intptr_t>(obj) ;
} else {
// Marsaglia’s xor-shift scheme with thread-specific state
// This is probably the best overall implementation – we’ll
// likely make this the default in future releases.
unsigned t = Self->_hashStateX ;
t ^= (t << 11) ;
Self->_hashStateX = Self->_hashStateY ;
Self->_hashStateY = Self->_hashStateZ ;
Self->_hashStateZ = Self->_hashStateW ;
unsigned v = Self->_hashStateW ;
v = (v ^ (v >> 19)) ^ (t ^ (t >> 8)) ;
Self->_hashStateW = v ;
value = v ;
}

value &= markOopDesc::hash_mask;
if (value == 0) value = 0xBAD ;
assert (value != markOopDesc::no_hash, “invariant”) ;
TEVENT (hashCode: GENERATE) ;
return value;
}

对于OpenJDK8版本,其默认配置hg.openjdk.java.net/jdk8u/jdk8u… 为:

 product(intx, hashCode, 5,                                                </span>
“(Unstable) select hashCode generation algorithm”) </span>

其对应的hashCode计算方案为:

    // Marsaglia’s xor-shift scheme with thread-specific state
// This is probably the best overall implementation – we’ll
// likely make this the default in future releases.
unsigned t = Self->_hashStateX ;
t ^= (t << 11) ;
Self->_hashStateX = Self->_hashStateY ;
Self->_hashStateY = Self->_hashStateZ ;
Self->_hashStateZ = Self->_hashStateW ;
unsigned v = Self->_hashStateW ;
v = (v ^ (v >> 19)) ^ (t ^ (t >> 8)) ;
Self->_hashStateW = v ;
value = v ;

其中Thread->_hashStateX, Thread->_hashStateY, Thread->_hashStateZ, Thread->_hashStateW在hg.openjdk.java.net/jdk8u/jdk8u… 有定义:

   // thread-specific hashCode stream generator state - Marsaglia shift-xor form
_hashStateX = os::random() ;
_hashStateY = 842502087 ;
_hashStateZ = 0x8767 ; // (int)(3579807591LL & 0xffff) ;
_hashStateW = 273326509 ;

所以,JDK8 的默认hashCode的计算方法是通过和当前线程有关的一个随机数+三个确定值,运用Marsaglia’s xorshift scheme随机数算法得到的一个随机数。对xorshift算法有兴趣可以参考原论文:www.jstatsoft.org/article/vie…
xorshift是由George Marsaglia发现的一类伪随机数生成器,其通过移位和与或计算,能够在计算机上以极快的速度生成伪随机数序列。其算法的基本实现如下:

unsigned long xor128(){
static unsigned long x=123456789,y=362436069,z=521288629,w=88675123;
unsigned long t;
t=(xˆ(x<<11));x=y;y=z;z=w; return( w=(wˆ(w>>19))ˆ(tˆ(t>>8)) );

这就和上面计算hashCode的OpenJDK代码对应了起来。


5 . 其他几类hashCode计算方案:


if (hashCode == 0) {
// This form uses an unguarded global Park-Miller RNG,
// so it’s possible for two threads to race and generate the same RNG.
// On MP system we’ll have lots of RW access to a global, so the
// mechanism induces lots of coherency traffic.
value = os::random() ;
}


  • hashCode == 1
    此类方案将对象的内存地址,做移位运算后与一个随机数进行异或得到结果

if (hashCode == 1) {
// This variation has the property of being stable (idempotent)
// between STW operations. This can be useful in some of the 1-0
// synchronization schemes.
intptr_t addrBits = cast_from_oop<intptr_t>(obj) >> 3 ;
value = addrBits ^ (addrBits >> 5) ^ GVars.stwRandom ;
}


  • hashCode == 2
    此类方案返回固定的1

if (hashCode == 2) {
value = 1 ; // for sensitivity testing
}


  • hashCode == 3
    此类方案返回一个自增序列的当前值

if (hashCode == 3) {
value = ++GVars.hcSequence ;
}


  • hashCode == 4
    此类方案返回当前对象的内存地址

if (hashCode == 4) {
value = cast_from_oop<intptr_t>(obj) ;
}

可以通过在JVM启动参数中添加-XX:hashCode=4,改变默认的hashCode计算方式。



参考资料:
srvaroa.github.io/jvm/java/op…
en.wikipedia.org/wiki/Xorshi…
www.cnblogs.com/mengyou0304…
stackoverflow.com/questions/2…
hllvm.group.iteye.com/group/topic…



本文系统分析了一种融合卷积神经网络、长短期记忆网络与注意力机制的时序预测模型在金融市场的应用价值。该模型通过多层次特征提取与动态权重分配,显著提升了股价趋势分析的准确性。在特征提取层面,卷积神经网络组件专门负责捕捉时间序列中的局部波动模式。其卷积核可识别出历史价格数据中具有预测价值的短期形态特征,这些特征往往对应着特定的市场行为模式。通过多层卷积运算,系统能够构建出具有判别力的特征表示,为后续时序分析奠定基础。针对长期依赖关系建模,长短期记忆网络模块采用门控机制实现对历史信息的筛选与记忆。其独特的遗忘门、输入门和输出门结构使模型能够自主决定信息保留程度,有效解决了传统循环神经网络在长序列训练中的梯度消失问题。这种设计特别适合金融市场数据中存在的周期性波动和长期趋势变化。注意力机制的引入进一步优化了模型的信息处理策略。该组件通过计算不同时间步的贡献度权重,使模型能够动态聚焦于对预测目标最具影响力的关键时段。这种自适应聚焦能力尤其适用于处理突发事件对股价造成的异常波动,显著提升了模型对市场异常状态的响应灵敏度。从架构设计角度观察,这种混合模型实现了空间特征与时间特征的协同提取。卷积神经网络输出的局部特征作为长短期记忆网络的输入,再经由注意力机制进行重要性加权,形成完整的多尺度分析流程。这种分层处理方式较好地契合了金融时间序列中短期波动与长期趋势并存的复杂特性。在实践应用层面,此类预测系统需要充分考虑金融数据的特殊性质。市场噪声干扰、非线性动力学特征以及投资者情绪波动等因素都会对模型性能产生重要影响。因此,除模型结构优化外,还需要配套完善的特征工程方案、严格的超参数调优流程以及全面的泛化能力测试。需要特别强调的是,由于金融市场固有的随机性和复杂性,任何预测模型都应被视为辅助决策工具而非确定性预测装置。该研究为深度学习技术在量化金融领域的应用提供了有价值的参考框架,同时也揭示了将先进算法成功应用于实际金融场景所需满足的严谨性和持续优化要求。资源来源于网络分享,仅用于学习交流使用,请勿用于商业,如有侵权请联系我删除!
评论 4
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值