core-libs-dev  

Messages by Thread

• RFR: 8388527: Add "indistinguishable" cross-reference to Double's discussion of equality Joe Darcy
  • Re: RFR: 8388527: Add "indistinguishable" cross-reference to Double's discussion of equality Chen Liang
  • Re: RFR: 8388527: Add "indistinguishable" cross-reference to Double's discussion of equality Joe Darcy
  • Re: RFR: 8388527: Add "indistinguishable" cross-reference to Double's discussion of equality Chen Liang
  • Re: RFR: 8388527: Add "indistinguishable" cross-reference to Double's discussion of equality Dan Smith
  • Re: RFR: 8388527: Add "indistinguishable" cross-reference to Double's discussion of equality Joe Darcy
  • Re: RFR: 8388527: Add "indistinguishable" cross-reference to Double's discussion of equality [v2] Dan Smith
  • Re: RFR: 8388527: Add "indistinguishable" cross-reference to Double's discussion of equality [v2] Joe Darcy
  • Re: RFR: 8388527: Add "indistinguishable" cross-reference to Double's discussion of equality [v2] Chen Liang
  • Re: RFR: 8388527: Add "indistinguishable" cross-reference to Double's discussion of equality Joe Darcy
  • Re: RFR: 8388527: Add "indistinguishable" cross-reference to Double's discussion of equality Joe Darcy
  • Integrated: 8388527: Add "indistinguishable" cross-reference to Double's discussion of equality Joe Darcy
• Withdrawn: 8317278: JVM implementation of value objects David Simms
• Withdrawn: 8317277: Java language implementation of value objects David Simms
• RFR: 8389282: Add explicit statement on null-handling of structural types in java.util.function Joe Darcy
  • Re: RFR: 8389282: Add explicit statement on null-handling of structural types in java.util.function Joe Darcy
  • Re: RFR: 8389282: Add explicit statement on null-handling of structural types in java.util.function [v2] Joe Darcy
  • Re: RFR: 8389282: Add explicit statement on null-handling of structural types in java.util.function [v2] Chen Liang
  • Re: RFR: 8389282: Add explicit statement on null-handling of structural types in java.util.function [v2] Joe Darcy
  • Re: RFR: 8389282: Add explicit statement on null-handling of structural types in java.util.function [v2] Jean-Noël Rouvignac
  • Re: RFR: 8389282: Add explicit statement on null-handling of structural types in java.util.function [v2] Joe Darcy
  • Re: RFR: 8389282: Add explicit statement on null-handling of structural types in java.util.function [v2] Per Minborg
  • Re: RFR: 8389282: Add explicit statement on null-handling of structural types in java.util.function [v2] Joe Darcy
  • Re: RFR: 8389282: Add explicit statement on null-handling of structural types in java.util.function [v2] Alan Bateman
  • Re: RFR: 8389282: Add explicit statement on null-handling of structural types in java.util.function [v2] Alan Bateman
  • Re: RFR: 8389282: Add explicit statement on null-handling of structural types in java.util.function [v2] Joe Darcy
  • Re: RFR: 8389282: Add explicit statement on null-handling of structural types in java.util.function [v3] Joe Darcy
  • Re: RFR: 8389282: Add explicit statement on null-handling of structural types in java.util.function [v4] Joe Darcy
• RFR: 8389466: Clarify Class::desiredAssertionStatus for primitive and array types Chen Liang
  • Re: RFR: 8389466: Clarify Class::desiredAssertionStatus for primitive and array types Chen Liang
  • Re: RFR: 8389466: Clarify Class::desiredAssertionStatus for primitive and array types [v2] Chen Liang
  • Re: RFR: 8389466: Clarify Class::desiredAssertionStatus for primitive and array types [v2] Alan Bateman
  • Re: RFR: 8389466: Clarify Class::desiredAssertionStatus for primitive and array types [v2] Chen Liang
  • Integrated: 8389466: Clarify Class::desiredAssertionStatus for primitive and array types Chen Liang
• RFR: 8389468: Introduce Class::isClassOrInterface Chen Liang
  • Re: RFR: 8389468: Introduce Class::isClassOrInterface Chen Liang
  • Re: RFR: 8389468: Introduce Class::isClassOrInterface Coleen Phillimore
  • Re: RFR: 8389468: Introduce Class::isClassOrInterface Chen Liang
  • Re: RFR: 8389468: Introduce Class::isClassOrInterface [v2] Chen Liang
  • Re: RFR: 8389468: Introduce Class::isClassOrInterface [v2] Jaikiran Pai
  • Re: RFR: 8389468: Introduce Class::isClassOrInterface [v2] Chen Liang
  • Re: RFR: 8389468: Introduce Class::isClassOrInterface [v2] Joe Darcy
  • Re: RFR: 8389468: Introduce Class::isClassOrInterface [v2] Chen Liang
  • Re: RFR: 8389468: Introduce Class::isClassOrInterface [v2] Joe Darcy
  • Re: RFR: 8389468: Introduce Class::isClassOrInterface [v2] Chen Liang
  • Re: RFR: 8389468: Introduce Class::isClassOrInterface [v3] Chen Liang
  • Re: RFR: 8389468: Introduce Class::isClassOrInterface [v3] Alan Bateman
  • Re: RFR: 8389468: Introduce Class::isClassOrInterface [v3] Chen Liang
  • Re: RFR: 8389468: Introduce Class::isClassOrInterface [v4] Chen Liang
  • Re: RFR: 8389468: Introduce Class::isClassOrInterface [v4] Shaojin Wen
  • Re: RFR: 8389468: Introduce Class::isClassOrInterface [v4] David Holmes
  • Re: RFR: 8389468: Introduce Class::isClassOrInterface [v4] ExE Boss
  • Re: RFR: 8389468: Introduce Class::isClassOrInterface [v4] Chen Liang
  • Re: RFR: 8389468: Introduce Class::isClassOrInterface [v5] Chen Liang
  • Re: RFR: 8389468: Introduce Class::isClassOrInterface [v5] Chen Liang
  • Re: RFR: 8389468: Introduce Class::isClassOrInterface [v5] Chen Liang
• RFR: 8389455: Avoid local initialized unused variables in libjimage Matthias Baesken
  • Re: RFR: 8389455: Avoid local initialized unused variables in libjimage Matthias Baesken
  • Re: RFR: 8389455: Avoid local initialized unused variables in libjimage [v2] Matthias Baesken
  • Re: RFR: 8389455: Avoid local initialized unused variables in libjimage [v2] Goetz Lindenmaier
  • Re: RFR: 8389455: Avoid local initialized unused variables in libjimage [v2] Matthias Baesken
  • Integrated: 8389455: Avoid local initialized unused variables in libjimage Matthias Baesken
• Integrated: 8388991: Adjust relauncher.c to avoid unused variable and init STARTUPINFO as suggested Matthias Baesken
• RFR: 8357394: Add JDK specific property for external resource access Joe Wang
  • Re: RFR: 8357394: Add JDK specific property for external resource access Alan Bateman
  • Re: RFR: 8357394: Add JDK specific property for external resource access Alan Bateman
  • Re: RFR: 8357394: Add JDK specific property for external resource access [v2] Joe Wang
  • Re: RFR: 8357394: Add JDK specific property for external resource access [v2] Alan Bateman
  • Re: RFR: 8357394: Add JDK specific property for external resource access [v3] Joe Wang
  • Re: RFR: 8357394: Add JDK specific property for external resource access Alan Bateman
  • Re: RFR: 8357394: Add JDK specific property for external resource access [v2] Joe Wang
  • Re: RFR: 8357394: Add JDK specific property for external resource access Alan Bateman
  • Re: RFR: 8357394: Add JDK specific property for external resource access Alan Bateman
  • Re: RFR: 8357394: Add JDK specific property for external resource access [v2] Joe Wang
  • Re: RFR: 8357394: Add JDK specific property for external resource access [v2] Joe Wang
  • Re: RFR: 8357394: Add JDK specific property for external resource access [v3] Joe Wang
• Re: RFR: 8388991: Adjust relauncher.c to avoid unused variable and init STARTUPINFO as suggested David Holmes
  • Re: RFR: 8388991: Adjust relauncher.c to avoid unused variable and init STARTUPINFO as suggested Matthias Baesken
• RFR: 8388918: AArch64: Optimize vector and vector mask (A & B) ^ B to BIC instruction Eric Fang
  • Re: RFR: 8388918: AArch64: Optimize vector and vector mask (A & B) ^ B to BIC instruction Dean Long
  • Re: RFR: 8388918: AArch64: Optimize vector and vector mask (A & B) ^ B to BIC instruction Eric Fang
  • Re: RFR: 8388918: AArch64: Optimize vector and vector mask (A & B) ^ B to BIC instruction Andrew Haley
  • Re: RFR: 8388918: AArch64: Optimize vector and vector mask (A & B) ^ B to BIC instruction Eric Fang
  • Re: RFR: 8388918: C2: Optimize vector and vector mask (A & B) ^ B to ~A & B [v2] Eric Fang
  • Re: RFR: 8388918: C2: Optimize vector and vector mask (A & B) ^ B to ~A & B [v2] Eric Fang
  • Re: RFR: 8388918: C2: Optimize vector and vector mask (A & B) ^ B to ~A & B [v2] Quan Anh Mai
  • Re: RFR: 8388918: C2: Optimize vector and vector mask (A & B) ^ B to ~A & B [v2] Eric Fang
• RFR: 8387748: VectorAPI: AArch64: Improve VectorMask.lastTrue() SVE implementation Eric Fang
• RFR: 8389110: java/nio/file/FileStore/Basic.java testEnumerateFileStores fails in container: FileStores should be unique Shiv Shah
  • Re: RFR: 8389110: java/nio/file/FileStore/Basic.java testEnumerateFileStores fails in container: FileStores should be unique Ekaterina Pavlova
  • Re: RFR: 8389110: java/nio/file/FileStore/Basic.java testEnumerateFileStores fails in container: FileStores should be unique Shiv Shah
• Re: RFR: 8373118: Test java/lang/Thread/virtual/Starvation.java timed out [v113] Doug Lea
• Re: RFR: 8317277: Java language implementation of value objects [v10] David Simms
  • Re: RFR: 8317277: Java language implementation of value objects [v10] David Simms
• Re: RFR: 8317278: JVM implementation of value objects [v10] David Simms
  • Re: RFR: 8317278: JVM implementation of value objects [v10] David Simms
• RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver Coleen Phillimore
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver Chen Liang
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v2] Coleen Phillimore
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v2] Coleen Phillimore
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v2] Chen Liang
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v2] David Holmes
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v2] David Holmes
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v2] David Holmes
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v2] David Holmes
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v2] Coleen Phillimore
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v2] Coleen Phillimore
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v2] Chen Liang
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v3] Coleen Phillimore
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v3] Alan Bateman
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v3] Chen Liang
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v3] Alan Bateman
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v3] Chen Liang
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v3] Stuart Marks
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v3] Alan Bateman
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v3] Coleen Phillimore
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v3] Alan Bateman
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v3] Coleen Phillimore
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v3] Chen Liang
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v3] Coleen Phillimore
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v3] David Holmes
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v3] Chen Liang
  • Re: RFR: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver [v3] Coleen Phillimore
  • Integrated: 8389259: Class::desiredAssertionStatus asserts with primitive or array class receiver Coleen Phillimore
• [External] : jlink man page issues Pavel Rappo
  • Re: [External] : jlink man page issues Alan Bateman
  • Re: [External] : jlink man page issues Pavel Rappo
• RFR: 8389250: Potential race in LazyConstant.Mutexes.releaseMutex Per Minborg
  • Re: RFR: 8389250: Potential race in LazyConstant.Mutexes.releaseMutex [v2] Per Minborg
  • Re: RFR: 8389250: Potential race in LazyConstant.Mutexes.releaseMutex [v2] David Holmes
  • Re: RFR: 8389250: Potential race in LazyConstant.Mutexes.releaseMutex [v2] Per Minborg
  • Re: RFR: 8389250: Potential race in LazyConstant.Mutexes.releaseMutex [v2] David Holmes
  • Re: RFR: 8389250: Improve logic and efficiency in LazyConstant.Mutexes [v2] Per Minborg
  • Re: RFR: 8389250: Improve logic and efficiency in LazyConstant.Mutexes [v2] Per Minborg
  • Re: RFR: 8389250: Improve logic and efficiency in LazyConstant.Mutexes [v3] Per Minborg
  • Re: RFR: 8389250: Improve logic and efficiency in LazyCollections.Mutexes [v3] David Holmes
  • Re: RFR: 8389250: Improve logic and efficiency in LazyCollections.Mutexes [v3] Viktor Klang
  • Re: RFR: 8389250: Improve logic and efficiency in LazyCollections.Mutexes [v3] Viktor Klang
  • Re: RFR: 8389250: Improve logic and efficiency in LazyCollections.Mutexes [v3] ExE Boss
  • Re: RFR: 8389250: Improve logic and efficiency in LazyCollections.Mutexes [v4] Per Minborg
  • Re: RFR: 8389250: Improve logic and efficiency in LazyCollections.Mutexes [v4] Viktor Klang
• Re: RFR: 8388991: Adjust relauncher.c to avoid unused variable and init PROCESS_INFORMATION as suggested David Holmes
  • Re: RFR: 8388991: Adjust relauncher.c to avoid unused variable and init STARTUPINFO as suggested Matthias Baesken
  • Re: RFR: 8388991: Adjust relauncher.c to avoid unused variable and init PROCESS_INFORMATION as suggested Thomas Stuefe
  • Re: RFR: 8388991: Adjust relauncher.c to avoid unused variable and init PROCESS_INFORMATION as suggested Alan Bateman
  • Re: RFR: 8388991: Adjust relauncher.c to avoid unused variable and init STARTUPINFO as suggested Matthias Baesken
  • Re: RFR: 8388991: Adjust relauncher.c to avoid unused variable and init STARTUPINFO as suggested Alan Bateman
• RFR: 8388415: Typo "sufficent" (instead of "sufficient") appears on https://docs.oracle.com/en/java/javase/26/docs/api/java.base/java/lang/classfile/attribute/package-summary.html by1361092
  • Re: RFR: 8388415: Typo "sufficent" (instead of "sufficient") appears on https://docs.oracle.com/en/java/javase/26/docs/api/java.base/java/lang/classfile/attribute/package-summary.html Chen Liang
  • Re: RFR: 8388415: Typo "sufficent" (instead of "sufficient") appears on https://docs.oracle.com/en/java/javase/26/docs/api/java.base/java/lang/classfile/attribute/package-summary.html Amit Kumar
  • Re: RFR: 8388415: Typo "sufficent" (instead of "sufficient") in package-info.java of java.lang.classfile.attribute package by1361092
  • Re: RFR: 8388415: Typo "sufficent" (instead of "sufficient") in package-info.java of java.lang.classfile.attribute package Chen Liang
  • Re: RFR: 8388415: Typo "sufficent" (instead of "sufficient") in package-info.java of java.lang.classfile.attribute package duke
  • Re: RFR: 8388415: Typo "sufficent" (instead of "sufficient") in package-info.java of java.lang.classfile.attribute package by1361092
  • Re: RFR: 8388415: Typo "sufficent" (instead of "sufficient") in package-info.java of java.lang.classfile.attribute package Amit Kumar
  • Integrated: 8388415: Typo "sufficent" (instead of "sufficient") in package-info.java of java.lang.classfile.attribute package by1361092
• RFR: 8389116: Improve comments on memory semantics in LazyCollections Per Minborg
  • Re: RFR: 8389116: Improve comments on memory semantics in LazyCollections Sergey Bylokhov
  • Re: RFR: 8389116: Improve comments on memory semantics in LazyCollections Sergey Bylokhov
  • Re: RFR: 8389116: Improve comments on memory semantics in LazyCollections Chen Liang
  • Re: RFR: 8389116: Improve comments on memory semantics in LazyCollections David Holmes
  • Re: RFR: 8389116: Improve comments on memory semantics in LazyCollections Per Minborg
  • Withdrawn: 8389116: Improve comments on memory semantics in LazyCollections Per Minborg
• RFR: 8388794: Short display name tests for zones with explicit DST offsets Naoto Sato
  • Re: RFR: 8388794: Short display name tests for zones with explicit DST offsets Iris Clark
  • Re: RFR: 8388794: Short display name tests for zones with explicit DST offsets Justin Lu
  • Integrated: 8388794: Short display name tests for zones with explicit DST offsets Naoto Sato
  • Re: RFR: 8388794: Short display name tests for zones with explicit DST offsets Naoto Sato
• Re: RFR: 8373118: Test java/lang/Thread/virtual/Starvation.java timed out [v112] Doug Lea
• [jdk27] RFR: 8379830: The warnings for value-based classes need updating to include use of the Reference API Chen Liang
  • Re: [jdk27] RFR: 8379830: The warnings for value-based classes need updating to include use of the Reference API Joe Darcy
  • Re: [jdk27] RFR: 8379830: The warnings for value-based classes need updating to include use of the Reference API Chen Liang
  • Re: [jdk27] RFR: 8379830: The warnings for value-based classes need updating to include use of the Reference API Roger Riggs
  • Re: [jdk27] RFR: 8379830: The warnings for value-based classes need updating to include use of the Reference API [v2] Chen Liang
  • Re: [jdk27] RFR: 8379830: The warnings for value-based classes need updating to include use of the Reference API [v2] Chen Liang
  • Re: [jdk27] RFR: 8379830: The warnings for value-based classes need updating to include use of the Reference API [v2] David Holmes
  • Re: [jdk27] RFR: 8379830: The warnings for value-based classes need updating to include use of the Reference API [v2] Chen Liang
  • [jdk27] Integrated: 8379830: The warnings for value-based classes need updating to include use of the Reference API Chen Liang
• Re: RFR: 8384082: Incorrect surrogate handling in Pattern.hasBaseCharacter for word boundaries [v4] Liam Miller-Cushon
• [jdk27] RFR: 8387722: The race during initialization or lazy constants in and Map/Set Per Minborg
  • Re: [jdk27] RFR: 8387722: The race during initialization or lazy constants in and Map/Set Jaikiran Pai
  • Re: [jdk27] RFR: 8387722: The race during initialization or lazy constants in and Map/Set Alan Bateman
  • [jdk27] Integrated: 8387722: The race during initialization or lazy constants in and Map/Set Per Minborg
• Re: RFR: 8373118: Test java/lang/Thread/virtual/Starvation.java timed out [v111] Doug Lea
• Re: RFR: 8373118: Test java/lang/Thread/virtual/Starvation.java timed out [v110] Doug Lea
• Re: RFR: 8373118: Test java/lang/Thread/virtual/Starvation.java timed out [v109] Doug Lea
• Integrated: 8364025: MinMaxVector clipping range benchmark highestInt/Long can overflow Galder Zamarreño
• New candidate JEP: 540: Simple JSON API (Incubator) Mark Reinhold
  • [External] : Re: New candidate JEP: 540: Simple JSON API (Incubator) Paul Bakker
• Re: RFR: 8373118: Test java/lang/Thread/virtual/Starvation.java timed out [v108] Doug Lea
• Integrated: 8388561: [s390x] Prevent accidental page table expansion Thomas Stuefe
• RFR: 8388810: Exceeding CachedRowSet max rows should only warn once Justin Lu
  • Re: RFR: 8388810: Exceeding CachedRowSet max rows should only warn once Justin Lu
  • Re: RFR: 8388810: Exceeding CachedRowSet max rows should only warn once Lance Andersen
  • Re: RFR: 8388810: Exceeding CachedRowSet max rows should only warn once Lance Andersen
  • Integrated: 8388810: Exceeding CachedRowSet max rows should only warn once Justin Lu
• RFR: 8388887: Migrate AtomicReferenceFieldUpdater to use VarHandle Chen Liang
  • Re: RFR: 8388887: Migrate AtomicReferenceFieldUpdater to use VarHandle Viktor Klang
  • Re: RFR: 8388887: Migrate AtomicReferenceFieldUpdater to use VarHandle Alan Bateman
  • Re: RFR: 8388887: Migrate AtomicReferenceFieldUpdater to use VarHandle Chen Liang

• Earlier messages
• Later messages