valhalla-dev  

Messages by Thread

• • Re: [lworld] RFR: 8387661: [lworld] move generate_return_value_stub() to SharedRuntime [v5] Andrew Dinn
  • Re: [lworld] RFR: 8387661: [lworld] move generate_return_value_stub() to SharedRuntime [v5] Roland Westrelin
  • Re: [lworld] RFR: 8387661: [lworld] move generate_return_value_stub() to SharedRuntime [v5] Tobias Hartmann
  • Re: [lworld] RFR: 8387661: [lworld] move generate_return_value_stub() to SharedRuntime [v5] Andrew Dinn
  • Re: [lworld] RFR: 8387661: [lworld] move generate_return_value_stub() to SharedRuntime [v5] Tobias Hartmann
  • [lworld] Integrated: 8387661: [lworld] move generate_return_value_stub() to SharedRuntime Roland Westrelin
• [lworld] RFR: 8387612: [lworld] C2: assert(array_type->is_flat() || ideal.ctrl()->in(0)->as_If()->is_flat_array_check(&_gvn)) failed: Should be found Christian Hagedorn
  • Re: [lworld] RFR: 8387612: [lworld] C2: assert(array_type->is_flat() || ideal.ctrl()->in(0)->as_If()->is_flat_array_check(&_gvn)) failed: Should be found Tobias Hartmann
  • Re: [lworld] RFR: 8387612: [lworld] C2: assert(array_type->is_flat() || ideal.ctrl()->in(0)->as_If()->is_flat_array_check(&_gvn)) failed: Should be found Christian Hagedorn
  • Re: [lworld] RFR: 8387612: [lworld] C2: assert(array_type->is_flat() || ideal.ctrl()->in(0)->as_If()->is_flat_array_check(&_gvn)) failed: Should be found [v2] Christian Hagedorn
  • Re: [lworld] RFR: 8387612: [lworld] C2: assert(array_type->is_flat() || ideal.ctrl()->in(0)->as_If()->is_flat_array_check(&_gvn)) failed: Should be found [v2] Christian Hagedorn
  • [lworld] Integrated: 8387612: [lworld] C2: assert(array_type->is_flat() || ideal.ctrl()->in(0)->as_If()->is_flat_array_check(&_gvn)) failed: Should be found Christian Hagedorn
• [lworld] RFR: 8387657: [lworld] Object Tags section of JVMTI spec should make it clear that ObjectFree event is not sent for value objects Alan Bateman
  • Re: [lworld] RFR: 8387657: [lworld] Object Tags section of JVMTI spec should make it clear that ObjectFree event is not sent for value objects Serguei Spitsyn
  • Re: [lworld] RFR: 8387657: [lworld] Object Tags section of JVMTI spec should make it clear that ObjectFree event is not sent for value objects Alan Bateman
  • Re: [lworld] RFR: 8387657: [lworld] Object Tags section of JVMTI spec should make it clear that ObjectFree event is not sent for value objects duke
  • Re: [lworld] RFR: 8387657: [lworld] Object Tags section of JVMTI spec should make it clear that ObjectFree event is not sent for value objects Chris Plummer
  • [lworld] Integrated: 8387657: [lworld] Object Tags section of JVMTI spec should make it clear that ObjectFree event is not sent for value objects Alan Bateman
• [lworld] RFR: 8387458: [lworld] vmTestbase/nsk/jdi/Accessible/modifiers/modifiers001 failed after JDK-8387389 Chris Plummer
  • Re: [lworld] RFR: 8387458: [lworld] vmTestbase/nsk/jdi/Accessible/modifiers/modifiers001 failed after JDK-8387389 David Holmes
  • Re: [lworld] RFR: 8387458: [lworld] vmTestbase/nsk/jdi/Accessible/modifiers/modifiers001 failed after JDK-8387389 Alan Bateman
  • Re: [lworld] RFR: 8387458: [lworld] vmTestbase/nsk/jdi/Accessible/modifiers/modifiers001 failed after JDK-8387389 Chris Plummer
  • [lworld] Integrated: 8387458: [lworld] vmTestbase/nsk/jdi/Accessible/modifiers/modifiers001 failed after JDK-8387389 Chris Plummer
• [lworld] RFR: 8387350: [lworld] ObjectOutputStream.writeObject() doesn't throw InvalidClassException for Serializable instance with strict init fields Chen Liang
  • Re: [lworld] RFR: 8387350: [lworld] ObjectOutputStream.writeObject() doesn't throw InvalidClassException for Serializable instance with strict init fields Alan Bateman
  • Re: [lworld] RFR: 8387350: [lworld] ObjectOutputStream.writeObject() doesn't throw InvalidClassException for Serializable instance with strict init fields ExE Boss
  • Re: [lworld] RFR: 8387350: [lworld] ObjectOutputStream.writeObject() doesn't throw InvalidClassException for Serializable instance with strict init fields Chen Liang
  • Re: [lworld] RFR: 8387350: [lworld] ObjectOutputStream.writeObject() doesn't throw InvalidClassException for Serializable instance with strict init fields Jaikiran Pai
  • Re: [lworld] RFR: 8387350: [lworld] ObjectOutputStream.writeObject() doesn't throw InvalidClassException for Serializable instance with strict init fields [v2] Chen Liang
  • Re: [lworld] RFR: 8387350: [lworld] ObjectOutputStream.writeObject() doesn't throw InvalidClassException for Serializable instance with strict init fields [v2] Chen Liang
  • Re: [lworld] RFR: 8387350: [lworld] ObjectOutputStream.writeObject() doesn't throw InvalidClassException for Serializable instance with strict init fields [v2] Chen Liang
  • Re: [lworld] RFR: 8387350: [lworld] ObjectOutputStream.writeObject() doesn't throw InvalidClassException for Serializable instance with strict init fields [v2] Alan Bateman
  • Re: [lworld] RFR: 8387350: [lworld] ObjectOutputStream.writeObject() doesn't throw InvalidClassException for Serializable instance with strict init fields [v2] Jaikiran Pai
  • Re: [lworld] RFR: 8387350: [lworld] ObjectOutputStream.writeObject() doesn't throw InvalidClassException for Serializable instance with strict init fields [v2] Tobias Hartmann
  • Re: [lworld] RFR: 8387350: [lworld] ObjectOutputStream.writeObject() doesn't throw InvalidClassException for Serializable instance with strict init fields [v2] Chen Liang
  • Re: [lworld] RFR: 8387350: [lworld] ObjectOutputStream.writeObject() doesn't throw InvalidClassException for Serializable instance with strict init fields [v2] Alan Bateman
  • Re: [lworld] RFR: 8387350: [lworld] ObjectOutputStream.writeObject() doesn't throw InvalidClassException for Serializable instance with strict init fields [v2] Chen Liang
  • [lworld] Integrated: 8387350: [lworld] ObjectOutputStream.writeObject() doesn't throw InvalidClassException for Serializable instance with strict init fields Chen Liang
• git: openjdk/valhalla: lworld: 8387484: [lworld] javac should warn on use of value classes Chen Liang
• [lworld] RFR: 8387629: [lworld] Don't use apiNote for some recent JDI spec updates Chris Plummer
  • Re: [lworld] RFR: 8387629: [lworld] Don't use apiNote for some recent JDI spec updates Serguei Spitsyn
  • Re: [lworld] RFR: 8387629: [lworld] Don't use apiNote for some recent JDI spec updates Serguei Spitsyn
  • Re: [lworld] RFR: 8387629: [lworld] Don't use apiNote for some recent JDI spec updates Alan Bateman
  • Re: [lworld] RFR: 8387629: [lworld] Don't use apiNote for some recent JDI spec updates Chris Plummer
  • Re: [lworld] RFR: 8387629: [lworld] Don't use apiNote for some recent JDI spec updates Alan Bateman
  • Re: [lworld] RFR: 8387629: [lworld] Don't use apiNote for some recent JDI spec updates [v3] Chris Plummer
  • Re: [lworld] RFR: 8387629: [lworld] Don't use apiNote for some recent JDI spec updates [v3] Alan Bateman
  • Re: [lworld] RFR: 8387629: [lworld] Don't use apiNote for some recent JDI spec updates [v2] Chris Plummer
  • Re: [lworld] RFR: 8387629: [lworld] Don't use apiNote for some recent JDI spec updates [v3] Chris Plummer
  • Re: [lworld] RFR: 8387629: [lworld] Don't use apiNote for some recent JDI spec updates [v3] Alan Bateman
  • Re: [lworld] RFR: 8387629: [lworld] Don't use apiNote for some recent JDI spec updates [v4] Chris Plummer
  • Re: [lworld] RFR: 8387629: [lworld] Don't use apiNote for some recent JDI spec updates [v4] Alan Bateman
  • Re: [lworld] RFR: 8387629: [lworld] Don't use apiNote for some recent JDI spec updates [v4] Serguei Spitsyn
  • Re: [lworld] RFR: 8387629: [lworld] Don't use apiNote for some recent JDI spec updates [v4] Chris Plummer
  • [lworld] Integrated: 8387629: [lworld] Don't use apiNote for some recent JDI spec updates Chris Plummer
• [lworld] RFR: 8387624: [lworld] cherry-pick JDK-8387265 G1: Shutdown during concurrent cycle leaves SATB queues in inconsistent state Daniel D . Daugherty
  • Re: [lworld] RFR: 8387624: [lworld] cherry-pick JDK-8387265 G1: Shutdown during concurrent cycle leaves SATB queues in inconsistent state Frederic Parain
  • Re: [lworld] RFR: 8387624: [lworld] cherry-pick JDK-8387265 G1: Shutdown during concurrent cycle leaves SATB queues in inconsistent state Daniel D . Daugherty
  • [lworld] Integrated: 8387624: [lworld] cherry-pick JDK-8387265 G1: Shutdown during concurrent cycle leaves SATB queues in inconsistent state Daniel D . Daugherty
• [lworld] RFR: 8386972: [lworld] Finalizer should not be registered for value objects Frederic Parain
  • Re: [lworld] RFR: 8386972: [lworld] Finalizer should not be registered for value objects Alan Bateman
  • Re: [lworld] RFR: 8386972: [lworld] Finalizer should not be registered for value objects Dan Heidinga
  • Re: [lworld] RFR: 8386972: [lworld] Finalizer should not be registered for value objects Dan Heidinga
  • Re: [lworld] RFR: 8386972: [lworld] Finalizer should not be registered for value objects ExE Boss
  • Re: [lworld] RFR: 8386972: [lworld] Finalizer should not be registered for value objects Alan Bateman
  • Re: [lworld] RFR: 8386972: [lworld] Finalizer should not be registered for value objects David Holmes
  • Re: [lworld] RFR: 8386972: [lworld] Finalizer should not be registered for value objects David Holmes
  • Re: [lworld] RFR: 8386972: [lworld] Finalizer should not be registered for value objects Jaikiran Pai
  • Re: [lworld] RFR: 8386972: [lworld] Finalizer should not be registered for value objects Coleen Phillimore
  • Re: [lworld] RFR: 8386972: [lworld] Finalizer should not be registered for value objects Frederic Parain
  • [lworld] Integrated: 8386972: [lworld] Finalizer should not be registered for value objects Frederic Parain
  • Re: [lworld] RFR: 8386972: [lworld] Finalizer should not be registered for value objects David Holmes
• [lworld] RFR: 8386874: [lworld] Clarify documentation of InstanceKlass layout in instanceKlass.hpp Coleen Phillimore
  • Re: [lworld] RFR: 8386874: [lworld] Clarify documentation of InstanceKlass layout in instanceKlass.hpp Lois Foltan
  • Re: [lworld] RFR: 8386874: [lworld] Clarify documentation of InstanceKlass layout in instanceKlass.hpp Coleen Phillimore
  • [lworld] Integrated: 8386874: [lworld] Clarify documentation of InstanceKlass layout in instanceKlass.hpp Coleen Phillimore
• [lworld] RFR: 8387556: [lworld] Update the JVMTI GetObjectMonitorUsage spec with a clarification on value objects impact Serguei Spitsyn
  • Re: [lworld] RFR: 8387556: [lworld] Update the JVMTI GetObjectMonitorUsage spec with a clarification on value objects impact [v2] Serguei Spitsyn
  • Re: [lworld] RFR: 8387556: [lworld] Update the JVMTI GetObjectMonitorUsage spec with a clarification on value objects impact [v3] Serguei Spitsyn
  • Re: [lworld] RFR: 8387556: [lworld] Update the JVMTI GetObjectMonitorUsage spec with a clarification on value objects impact [v3] Alan Bateman
  • Re: [lworld] RFR: JDK-8387556: [lworld] Update the JVMTI GetObjectMonitorUsage spec with a clarification on value objects impact [v3] Serguei Spitsyn
  • Re: [lworld] RFR: JDK-8387556: [lworld] Update the JVMTI GetObjectMonitorUsage spec with a clarification on value objects impact [v3] Alan Bateman
  • Re: [lworld] RFR: 8387556: [lworld] Update the JVMTI GetObjectMonitorUsage spec with a clarification on value objects impact [v3] Serguei Spitsyn
  • Re: [lworld] RFR: 8387556: [lworld] Update the JVMTI GetObjectMonitorUsage spec with a clarification on value objects impact [v3] Alan Bateman
  • Re: [lworld] RFR: JDK-8387556: [lworld] Update the JVMTI GetObjectMonitorUsage spec with a clarification on value objects impact [v4] Serguei Spitsyn
  • Re: [lworld] RFR: 8387556: [lworld] Update the JVMTI GetObjectMonitorUsage spec with a clarification on value objects impact [v5] Serguei Spitsyn
  • Re: [lworld] RFR: 8387556: [lworld] Update the JVMTI GetObjectMonitorUsage spec with a clarification on value objects impact [v5] Serguei Spitsyn
  • Re: [lworld] RFR: 8387556: [lworld] Update the JVMTI GetObjectMonitorUsage spec with a clarification on value objects impact [v5] Daniel D . Daugherty
  • Re: [lworld] RFR: 8387556: [lworld] Update the JVMTI GetObjectMonitorUsage spec with a clarification on value objects impact [v5] Serguei Spitsyn
  • Re: [lworld] RFR: 8387556: [lworld] Update the JVMTI GetObjectMonitorUsage spec with a clarification on value objects impact [v5] Chris Plummer
  • Re: [lworld] RFR: 8387556: [lworld] Update the JVMTI GetObjectMonitorUsage spec with a clarification on value objects impact [v5] Serguei Spitsyn
  • [lworld] Integrated: 8387556: [lworld] Update the JVMTI GetObjectMonitorUsage spec with a clarification on value objects impact Serguei Spitsyn
• [lworld] RFR: 8387564: [lworld] cherry-pick JDK-8387554 ProblemList vmTestbase/nsk/jvmti/unit/functions/Dispose/JvmtiTest/TestDescription.java in virtual thread configs Daniel D . Daugherty
  • Re: [lworld] RFR: 8387564: [lworld] cherry-pick JDK-8387554 ProblemList vmTestbase/nsk/jvmti/unit/functions/Dispose/JvmtiTest/TestDescription.java in virtual thread configs Leonid Mesnik
  • Re: [lworld] RFR: 8387564: [lworld] cherry-pick JDK-8387554 ProblemList vmTestbase/nsk/jvmti/unit/functions/Dispose/JvmtiTest/TestDescription.java in virtual thread configs Daniel D . Daugherty
  • [lworld] Integrated: 8387564: [lworld] cherry-pick JDK-8387554 ProblemList vmTestbase/nsk/jvmti/unit/functions/Dispose/JvmtiTest/TestDescription.java in virtual thread configs Daniel D . Daugherty
• [lworld] RFR: 8387552: [lworld] Add new capability to enable value objects support for JVMTI VMObjectAlloc and SampledObjectAlloc Serguei Spitsyn
  • Re: [lworld] RFR: 8387552: [lworld] Add new capability to enable value objects support for JVMTI VMObjectAlloc and SampledObjectAlloc Leonid Mesnik
  • Re: [lworld] RFR: 8387552: [lworld] Add new capability to enable value objects support for JVMTI VMObjectAlloc and SampledObjectAlloc Serguei Spitsyn
  • Re: [lworld] RFR: 8387552: [lworld] Add new capability to enable value objects support for JVMTI VMObjectAlloc and SampledObjectAlloc Serguei Spitsyn
  • Re: [lworld] RFR: 8387552: [lworld] Add new capability to enable value objects support for JVMTI VMObjectAlloc and SampledObjectAlloc Serguei Spitsyn
  • Re: [lworld] RFR: 8387552: [lworld] Add new capability to enable value objects support for JVMTI VMObjectAlloc and SampledObjectAlloc Leonid Mesnik
  • Re: [lworld] RFR: 8387552: [lworld] Add new capability to enable value objects support for JVMTI VMObjectAlloc and SampledObjectAlloc Serguei Spitsyn
  • Re: [lworld] RFR: 8387552: [lworld] Add new capability to enable value objects support for JVMTI VMObjectAlloc and SampledObjectAlloc Alan Bateman
  • Re: [lworld] RFR: 8387552: [lworld] Add new capability to enable value objects support for JVMTI VMObjectAlloc and SampledObjectAlloc Serguei Spitsyn
  • Re: [lworld] RFR: 8387552: [lworld] Add new capability to enable value objects support for JVMTI VMObjectAlloc and SampledObjectAlloc [v3] Alan Bateman
  • Re: [lworld] RFR: 8387552: [lworld] Add new capability to enable value objects support for JVMTI VMObjectAlloc and SampledObjectAlloc Alan Bateman
  • Re: [lworld] RFR: 8387552: [lworld] Add new capability to enable value objects support for JVMTI VMObjectAlloc and SampledObjectAlloc Serguei Spitsyn
  • Re: [lworld] RFR: 8387552: [lworld] Add new capability to enable value objects support for JVMTI VMObjectAlloc and SampledObjectAlloc [v2] Serguei Spitsyn
  • Re: [lworld] RFR: 8387552: [lworld] Add new capability to enable value objects support for JVMTI VMObjectAlloc and SampledObjectAlloc [v2] Chris Plummer
  • Re: [lworld] RFR: 8387552: [lworld] Add new capability to enable value objects support for JVMTI VMObjectAlloc and SampledObjectAlloc [v2] Alan Bateman
  • Re: [lworld] RFR: 8387552: [lworld] Add new capability to enable value objects support for JVMTI VMObjectAlloc and SampledObjectAlloc [v2] Serguei Spitsyn
  • Re: [lworld] RFR: 8387552: [lworld] Add new capability to enable value objects support for JVMTI VMObjectAlloc and SampledObjectAlloc [v3] Serguei Spitsyn
  • Re: [lworld] RFR: 8387552: [lworld] Add new capability to enable value objects support for JVMTI VMObjectAlloc and SampledObjectAlloc [v3] Chris Plummer
  • Re: [lworld] RFR: 8387552: [lworld] Add new capability to enable value objects support for JVMTI VMObjectAlloc and SampledObjectAlloc [v3] Serguei Spitsyn
  • [lworld] Integrated: 8387552: [lworld] Add new capability to enable value objects support for JVMTI VMObjectAlloc and SampledObjectAlloc Serguei Spitsyn
• [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor Alan Bateman
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor Serguei Spitsyn
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor Alan Bateman
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor Serguei Spitsyn
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor [v2] Alan Bateman
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor Alan Bateman
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor Serguei Spitsyn
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor David Holmes
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor Alan Bateman
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor [v2] Alan Bateman
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor [v3] Serguei Spitsyn
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor [v3] David Holmes
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor [v3] David Holmes
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor [v3] Alan Bateman
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor [v3] David Holmes
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor [v2] Alan Bateman
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor [v2] Chris Plummer
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor [v2] Alan Bateman
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor [v2] Chris Plummer
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor [v2] Alan Bateman
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor [v3] Alan Bateman
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor [v3] Serguei Spitsyn
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor [v3] Alan Bateman
  • Re: [lworld] RFR: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor [v3] duke
  • [lworld] Integrated: 8387540: [lworld] ForceEarlyReturnVoid should fail with OPAQUE_FRAME if target thread's top frame is value class constructor Alan Bateman
• [lworld] RFR: 8385112: [lworld] 8369044 fix missing for arm and ppc Daisuke Yamazaki
• [lworld] RFR: 8387495: [lworld] Typo in javadoc of jdk/internal/util/ReferencedKeyMap.java Jaikiran Pai
  • Re: [lworld] RFR: 8387495: [lworld] Typo in javadoc of jdk/internal/util/ReferencedKeyMap.java Alan Bateman
  • Re: [lworld] RFR: 8387495: [lworld] Typo in javadoc of jdk/internal/util/ReferencedKeyMap.java Chen Liang
  • Re: [lworld] RFR: 8387495: [lworld] Typo in javadoc of jdk/internal/util/ReferencedKeyMap.java Jaikiran Pai
  • Re: [lworld] RFR: 8387495: [lworld] Typo in javadoc of jdk/internal/util/ReferencedKeyMap.java duke
  • [lworld] Integrated: 8387495: [lworld] Typo in javadoc of jdk/internal/util/ReferencedKeyMap.java Jaikiran Pai
• [lworld] RFR: 8387488: [lworld] C2: acmp expansion fails with assert(replace != nullptr) failed: must succeed Tobias Hartmann
  • Re: [lworld] RFR: 8387488: [lworld] C2: acmp expansion fails with assert(replace != nullptr) failed: must succeed Tobias Hartmann
  • Re: [lworld] RFR: 8387488: [lworld] C2: acmp expansion fails with assert(replace != nullptr) failed: must succeed Quan Anh Mai
  • Re: [lworld] RFR: 8387488: [lworld] C2: acmp expansion fails with assert(replace != nullptr) failed: must succeed [v2] Quan Anh Mai
  • Re: [lworld] RFR: 8387488: [lworld] C2: acmp expansion fails with assert(replace != nullptr) failed: must succeed [v3] Tobias Hartmann
  • Re: [lworld] RFR: 8387488: [lworld] C2: acmp expansion fails with assert(replace != nullptr) failed: must succeed Marc Chevalier
  • Re: [lworld] RFR: 8387488: [lworld] C2: acmp expansion fails with assert(replace != nullptr) failed: must succeed Tobias Hartmann
  • Re: [lworld] RFR: 8387488: [lworld] C2: acmp expansion fails with assert(replace != nullptr) failed: must succeed [v2] Tobias Hartmann
  • Re: [lworld] RFR: 8387488: [lworld] C2: acmp expansion fails with assert(replace != nullptr) failed: must succeed [v3] Tobias Hartmann
  • Re: [lworld] RFR: 8387488: [lworld] C2: acmp expansion fails with assert(replace != nullptr) failed: must succeed [v3] Quan Anh Mai
  • Re: [lworld] RFR: 8387488: [lworld] C2: acmp expansion fails with assert(replace != nullptr) failed: must succeed [v3] Tobias Hartmann
  • [lworld] Integrated: 8387488: [lworld] C2: acmp expansion fails with assert(replace != nullptr) failed: must succeed Tobias Hartmann
• [lworld] RFR: 8386676: [lworld] Infinite loop when pushing inline types down though phis during IGVN Roland Westrelin
  • Re: [lworld] RFR: 8386676: [lworld] Infinite loop when pushing inline types down though phis during IGVN Tobias Hartmann
  • Re: [lworld] RFR: 8386676: [lworld] Infinite loop when pushing inline types down though phis during IGVN [v2] Roland Westrelin
  • Re: [lworld] RFR: 8386676: [lworld] Infinite loop when pushing inline types down though phis during IGVN [v2] Tobias Hartmann
  • Re: [lworld] RFR: 8386676: [lworld] Infinite loop when pushing inline types down though phis during IGVN [v2] Roland Westrelin
  • Re: [lworld] RFR: 8386676: [lworld] Infinite loop when pushing inline types down though phis during IGVN [v2] Tobias Hartmann
  • Re: [lworld] RFR: 8386676: [lworld] Infinite loop when pushing inline types down though phis during IGVN [v2] Roland Westrelin
  • Re: [lworld] RFR: 8386676: [lworld] Infinite loop when pushing inline types down though phis during IGVN Roland Westrelin
  • [lworld] Integrated: 8386676: [lworld] Infinite loop when pushing inline types down though phis during IGVN Roland Westrelin
• [lworld] RFR: 8387484: [lworld] javac should warn on use of value classes Jan Lahoda
  • Re: [lworld] RFR: 8387484: [lworld] javac should warn on use of value classes Maurizio Cimadamore
  • Re: [lworld] RFR: 8387484: [lworld] javac should warn on use of value classes Chen Liang
  • Re: [lworld] RFR: 8387484: [lworld] javac should warn on use of value classes [v2] Jan Lahoda
  • Re: [lworld] RFR: 8387484: [lworld] javac should warn on use of value classes Vicente Romero
  • Re: [lworld] RFR: 8387484: [lworld] javac should warn on use of value classes [v2] Jan Lahoda
  • Re: [lworld] RFR: 8387484: [lworld] javac should warn on use of value classes [v2] Chen Liang
  • Re: [lworld] RFR: 8387484: [lworld] javac should warn on use of value classes [v2] duke
  • [lworld] Integrated: 8387484: [lworld] javac should warn on use of value classes Jan Lahoda
• [lworld] RFR: 8387464: [lworld] Increase memlimit and unproblemlist TestValueConstruction.java Manuel Hässig
  • Re: [lworld] RFR: 8387464: [lworld] Increase memlimit and unproblemlist TestValueConstruction.java Tobias Hartmann
  • Re: [lworld] RFR: 8387464: [lworld] Increase memlimit and unproblemlist TestValueConstruction.java [v2] Manuel Hässig
  • Re: [lworld] RFR: 8387464: [lworld] Increase memlimit and unproblemlist TestValueConstruction.java [v2] Tobias Hartmann
  • Re: [lworld] RFR: 8387464: [lworld] Increase memlimit and unproblemlist TestValueConstruction.java [v2] Manuel Hässig
  • Re: [lworld] RFR: 8387464: [lworld] Increase memlimit and unproblemlist TestValueConstruction.java [v2] duke
  • Re: [lworld] RFR: 8387464: [lworld] Increase memlimit and unproblemlist TestValueConstruction.java Manuel Hässig
  • [lworld] Integrated: 8387464: [lworld] Increase memlimit and unproblemlist TestValueConstruction.java Manuel Hässig
• [lworld] RFR: 8386160: [lworld] Post jdk-27+25 compiler/valhalla/inlinetypes/TestIntrinsics.java#id4 assertion Quan Anh Mai
  • Re: [lworld] RFR: 8386160: [lworld] Post jdk-27+25 compiler/valhalla/inlinetypes/TestIntrinsics.java#id4 assertion Tobias Hartmann
  • Re: [lworld] RFR: 8386160: [lworld] Post jdk-27+25 compiler/valhalla/inlinetypes/TestIntrinsics.java#id4 assertion Quan Anh Mai
  • Re: [lworld] RFR: 8386160: [lworld] Post jdk-27+25 compiler/valhalla/inlinetypes/TestIntrinsics.java#id4 assertion Tobias Hartmann
  • Re: [lworld] RFR: 8386160: [lworld] Post jdk-27+25 compiler/valhalla/inlinetypes/TestIntrinsics.java#id4 assertion [v2] Quan Anh Mai
  • Re: [lworld] RFR: 8386160: [lworld] Post jdk-27+25 compiler/valhalla/inlinetypes/TestIntrinsics.java#id4 assertion [v2] Quan Anh Mai
  • [lworld] Integrated: 8386160: [lworld] Post jdk-27+25 compiler/valhalla/inlinetypes/TestIntrinsics.java#id4 assertion Quan Anh Mai
• [lworld] Integrated: 8387460: [lworld] ProblemList vmTestbase/nsk/jdi/Accessible/modifiers/modifiers001/TestDescription.java with enable-preview Daniel D . Daugherty
  • Re: [lworld] Integrated: 8387460: [lworld] ProblemList vmTestbase/nsk/jdi/Accessible/modifiers/modifiers001/TestDescription.java with enable-preview David Holmes
  • Re: [lworld] Integrated: 8387460: [lworld] ProblemList vmTestbase/nsk/jdi/Accessible/modifiers/modifiers001/TestDescription.java with enable-preview Daniel D . Daugherty
  • [lworld] Integrated: 8387460: [lworld] ProblemList vmTestbase/nsk/jdi/Accessible/modifiers/modifiers001/TestDescription.java with enable-preview Daniel D . Daugherty
• [lworld] RFR: 8387454: [lworld] Update Strict fields JEP number Chen Liang
  • Re: [lworld] RFR: 8387454: [lworld] Update Strict fields JEP number David Holmes
  • Re: [lworld] RFR: 8387454: [lworld] Update Strict fields JEP number Chen Liang

• Earlier messages
• Later messages