core-libs-dev  

Messages by Thread

• • Re: RFR: 8286562: GCC 12 reports some compiler warnings [v10] Yasumasa Suenaga
  • Re: RFR: 8286562: GCC 12 reports some compiler warnings [v10] Kim Barrett
  • Integrated: 8286562: GCC 12 reports some compiler warnings Yasumasa Suenaga
  • Re: Integrated: 8286562: GCC 12 reports some compiler warnings David Holmes
• RFR: 8286378: Address possibly lossy conversions in java.base Roger Riggs
  • Re: RFR: 8286378: Address possibly lossy conversions in java.base Naoto Sato
  • Re: RFR: 8286378: Address possibly lossy conversions in java.base Xue-Lei Andrew Fan
  • Re: RFR: 8286378: Address possibly lossy conversions in java.base Brian Burkhalter
  • Re: RFR: 8286378: Address possibly lossy conversions in java.base [v2] Roger Riggs
  • Re: RFR: 8286378: Address possibly lossy conversions in java.base [v2] Alan Bateman
  • Re: RFR: 8286378: Address possibly lossy conversions in java.base [v2] Adam Sotona
  • Re: RFR: 8286378: Address possibly lossy conversions in java.base [v3] Roger Riggs
  • Re: RFR: 8286378: Address possibly lossy conversions in java.base [v3] Brian Burkhalter
  • Re: RFR: 8286378: Address possibly lossy conversions in java.base [v3] Alan Bateman
  • Re: RFR: 8286378: Address possibly lossy conversions in java.base [v3] ExE Boss
  • Re: RFR: 8286378: Address possibly lossy conversions in java.base [v3] Alan Bateman
  • Re: RFR: 8286378: Address possibly lossy conversions in java.base [v3] Roger Riggs
  • Re: RFR: 8286378: Address possibly lossy conversions in java.base [v3] ExE Boss
  • Integrated: 8286378: Address possibly lossy conversions in java.base Roger Riggs
• RFR: 8286287: Reading file as UTF-16 causes Error which "shouldn't happen" Naoto Sato
  • Re: RFR: 8286287: Reading file as UTF-16 causes Error which "shouldn't happen" Jaikiran Pai
  • Re: RFR: 8286287: Reading file as UTF-16 causes Error which "shouldn't happen" Brian Burkhalter
  • Re: RFR: 8286287: Reading file as UTF-16 causes Error which "shouldn't happen" [v2] Naoto Sato
  • Re: RFR: 8286287: Reading file as UTF-16 causes Error which "shouldn't happen" [v2] Roger Riggs
  • Integrated: 8286287: Reading file as UTF-16 causes Error which "shouldn't happen" Naoto Sato
• Integrated: 8282701: Use Class.getInterfaces(false) where possible to reduce allocation pressure Сергей Цыпанов
• Re: RFR: 8282664: Unroll by hand StringUTF16, StringLatin1, and Arrays polynomial hash loops [v2] Ludovic Henry
• Re: RFR: 8282664: Unroll by hand StringUTF16, StringLatin1, and Arrays polynomial hash loops [v12] Ludovic Henry
  • Re: RFR: 8282664: Unroll by hand StringUTF16, StringLatin1, and Arrays polynomial hash loops [v12] ExE Boss
  • Re: RFR: 8282664: Unroll by hand StringUTF16, StringLatin1, and Arrays polynomial hash loops [v12] John R Rose
  • Re: RFR: 8282664: Unroll by hand StringUTF16, StringLatin1, and Arrays polynomial hash loops [v12] Paul Sandoz
  • Re: RFR: 8282664: Unroll by hand StringUTF16, StringLatin1, and Arrays polynomial hash loops [v12] Ludovic Henry
  • Re: RFR: 8282664: Unroll by hand StringUTF16, StringLatin1, and Arrays polynomial hash loops [v12] Paul Sandoz
• RFR: 8284493: Fix rounding error in computeNextExponential Chris Hennick
  • Re: RFR: 8284493: Fix rounding error in computeNextExponential Xin Liu
  • Re: RFR: 8284493: Fix rounding error in computeNextExponential Chris Hennick
  • Re: RFR: 8284493: Fix rounding error in computeNextExponential Andrey Turbanov
  • Re: RFR: 8284493: Fix rounding error in computeNextExponential Raffaello Giulietti
  • Re: RFR: 8284493: Fix rounding error in computeNextExponential [v2] Chris Hennick
  • Re: RFR: 8284493: Fix rounding error in computeNextExponential [v2] Chris Hennick
  • Re: RFR: 8284493: Fix rounding error in computeNextExponential [v2] Chris Hennick
  • Re: RFR: 8284493: Fix rounding error in computeNextExponential; use Math.fma(); use bounded version in computeNextGaussian [v2] Chris Hennick
  • Re: RFR: 8284493: Fix rounding error in computeNextExponential [v2] openjdk-notifier[bot]
  • Re: RFR: 8284493: Fix rounding error in computeNextExponential [v3] Chris Hennick
  • Re: RFR: 8284493: Fix rounding error in computeNextExponential [v4] Chris Hennick
• RFR: 8286212: Cgroup v1 initialization causes NPE on some systems Severin Gehwolf
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems Ioi Lam
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems Severin Gehwolf
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems Severin Gehwolf
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems Thomas Stuefe
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems Severin Gehwolf
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems [v2] Severin Gehwolf
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems [v2] Severin Gehwolf
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems [v2] Thomas Stuefe
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems [v2] Ioi Lam
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems [v2] Severin Gehwolf
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems [v2] Ioi Lam
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems [v2] Thomas Stuefe
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems [v2] Severin Gehwolf
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems [v2] Severin Gehwolf
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems [v2] Severin Gehwolf
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems [v2] Thomas Stuefe
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems [v2] Severin Gehwolf
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems [v3] Severin Gehwolf
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems [v3] Ioi Lam
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems [v3] Severin Gehwolf
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems [v3] Ioi Lam
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems [v3] Ioi Lam
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems [v3] Severin Gehwolf
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems [v3] Severin Gehwolf
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems [v3] Severin Gehwolf
  • Re: RFR: 8286212: Cgroup v1 initialization causes NPE on some systems [v3] Severin Gehwolf
• RFR: 8286474: Drop --enable-preview from Sealed Classes related tests Aleksey Shipilev
  • Re: RFR: 8286474: Drop --enable-preview from Sealed Classes related tests Jaikiran Pai
  • Re: RFR: 8286474: Drop --enable-preview from Sealed Classes related tests Alan Bateman
  • Re: RFR: 8286474: Drop --enable-preview from Sealed Classes related tests [v2] Aleksey Shipilev
  • Re: RFR: 8286474: Drop --enable-preview from Sealed Classes related tests [v2] Aleksey Shipilev
  • Re: RFR: 8286474: Drop --enable-preview from Sealed Classes related tests [v2] Alan Bateman
  • Re: RFR: 8286474: Drop --enable-preview from Sealed Classes related tests [v2] Jaikiran Pai
  • Re: RFR: 8286474: Drop --enable-preview from Sealed Classes related tests [v2] Mandy Chung
  • Re: RFR: 8286474: Drop --enable-preview from Sealed Classes related tests [v2] Lance Andersen
  • Re: RFR: 8286474: Drop --enable-preview from Sealed Classes related tests [v2] Aleksey Shipilev
  • Integrated: 8286474: Drop --enable-preview from Sealed Classes related tests Aleksey Shipilev
• Re: RFR: 8282664: Unroll by hand StringUTF16, StringLatin1, and Arrays polynomial hash loops [v11] Ludovic Henry
• RFR: 8286473: Drop --enable-preview from Record related tests Aleksey Shipilev
  • Re: RFR: 8286473: Drop --enable-preview from Record related tests Jaikiran Pai
  • Re: RFR: 8286473: Drop --enable-preview from Record related tests Alan Bateman
  • Re: RFR: 8286473: Drop --enable-preview from Record related tests [v2] Aleksey Shipilev
  • Re: RFR: 8286473: Drop --enable-preview from Record related tests [v2] Aleksey Shipilev
  • Re: RFR: 8286473: Drop --enable-preview from Record related tests [v2] Alan Bateman
  • Re: RFR: 8286473: Drop --enable-preview from Record related tests [v2] Jaikiran Pai
  • Re: RFR: 8286473: Drop --enable-preview from Record related tests [v2] Mandy Chung
  • Re: RFR: 8286473: Drop --enable-preview from Record related tests [v2] Aleksey Shipilev
  • Integrated: 8286473: Drop --enable-preview from Record related tests Aleksey Shipilev
• Re: RFR: 8282664: Unroll by hand StringUTF16 and StringLatin1 polynomial hash loops [v10] Ludovic Henry
• RFR: 8286441: Remove mode parameter from jdk.internal.perf.Perf.attach() Ioi Lam
  • Re: RFR: 8286441: Remove mode parameter from jdk.internal.perf.Perf.attach() Alan Bateman
  • Re: RFR: 8286441: Remove mode parameter from jdk.internal.perf.Perf.attach() [v2] Ioi Lam
  • Re: RFR: 8286441: Remove mode parameter from jdk.internal.perf.Perf.attach() Alan Bateman
  • Re: RFR: 8286441: Remove mode parameter from jdk.internal.perf.Perf.attach() Ioi Lam
  • Re: RFR: 8286441: Remove mode parameter from jdk.internal.perf.Perf.attach() Ioi Lam
  • Re: RFR: 8286441: Remove mode parameter from jdk.internal.perf.Perf.attach() Claes Redestad
  • Re: RFR: 8286441: Remove mode parameter from jdk.internal.perf.Perf.attach() [v2] Ioi Lam
  • Re: RFR: 8286441: Remove mode parameter from jdk.internal.perf.Perf.attach() [v2] Ioi Lam
  • Re: RFR: 8286441: Remove mode parameter from jdk.internal.perf.Perf.attach() [v2] Alan Bateman
  • Integrated: 8286441: Remove mode parameter from jdk.internal.perf.Perf.attach() Ioi Lam
• RFR: 8286279: [vectorapi] Only check index of masked lanes if offset is out of array boundary for masked store Xiaohong Gong
  • Re: RFR: 8286279: [vectorapi] Only check index of masked lanes if offset is out of array boundary for masked store Xiaohong Gong
  • Re: RFR: 8286279: [vectorapi] Only check index of masked lanes if offset is out of array boundary for masked store Paul Sandoz
  • Re: RFR: 8286279: [vectorapi] Only check index of masked lanes if offset is out of array boundary for masked store Xiaohong Gong
  • Re: RFR: 8286279: [vectorapi] Only check index of masked lanes if offset is out of array boundary for masked store Paul Sandoz
  • Re: RFR: 8286279: [vectorapi] Only check index of masked lanes if offset is out of array boundary for masked store Xiaohong Gong
  • Re: RFR: 8286279: [vectorapi] Only check index of masked lanes if offset is out of array boundary for masked store [v2] Xiaohong Gong
  • Re: RFR: 8286279: [vectorapi] Only check index of masked lanes if offset is out of array boundary for masked store Quan Anh Mai
  • Re: RFR: 8286279: [vectorapi] Only check index of masked lanes if offset is out of array boundary for masked store Xiaohong Gong
  • Re: RFR: 8286279: [vectorapi] Only check index of masked lanes if offset is out of array boundary for masked store Quan Anh Mai
  • Re: RFR: 8286279: [vectorapi] Only check index of masked lanes if offset is out of array boundary for masked store [v2] Xiaohong Gong
  • Re: RFR: 8286279: [vectorapi] Only check index of masked lanes if offset is out of array boundary for masked store [v2] Quan Anh Mai
  • Re: RFR: 8286279: [vectorapi] Only check index of masked lanes if offset is out of array boundary for masked store [v2] Xiaohong Gong
  • Re: RFR: 8286279: [vectorapi] Only check index of masked lanes if offset is out of array boundary for masked store [v2] Xiaohong Gong
  • Re: RFR: 8286279: [vectorapi] Only check index of masked lanes if offset is out of array boundary for masked store [v2] Paul Sandoz
  • Re: RFR: 8286279: [vectorapi] Only check index of masked lanes if offset is out of array boundary for masked store [v2] Xiaohong Gong
  • Re: RFR: 8286279: [vectorapi] Only check index of masked lanes if offset is out of array boundary for masked store [v2] Xiaohong Gong
  • Re: RFR: 8286279: [vectorapi] Only check index of masked lanes if offset is out of array boundary for masked store [v2] Xiaohong Gong
  • Re: RFR: 8286279: [vectorapi] Only check index of masked lanes if offset is out of array boundary for masked store [v3] Xiaohong Gong
  • Re: RFR: 8286279: [vectorapi] Only check index of masked lanes if offset is out of array boundary for masked store [v3] Paul Sandoz
  • Integrated: 8286279: [vectorapi] Only check index of masked lanes if offset is out of array boundary for masked store Xiaohong Gong
• RFR: 8286444: javac errors after JDK-8251329 are not helpful enough to find root cause Christoph Langer
  • Re: RFR: 8286444: javac errors after JDK-8251329 are not helpful enough to find root cause Christoph Langer
  • Re: RFR: 8286444: javac errors after JDK-8251329 are not helpful enough to find root cause Alan Bateman
  • Re: RFR: 8286444: javac errors after JDK-8251329 are not helpful enough to find root cause Lance Andersen
  • Re: RFR: 8286444: javac errors after JDK-8251329 are not helpful enough to find root cause Christoph Langer
  • Re: RFR: 8286444: javac errors after JDK-8251329 are not helpful enough to find root cause Alan Bateman
  • Re: RFR: 8286444: javac errors after JDK-8251329 are not helpful enough to find root cause Lance Andersen
  • Re: RFR: 8286444: javac errors after JDK-8251329 are not helpful enough to find root cause Lance Andersen
  • Re: RFR: 8286444: javac errors after JDK-8251329 are not helpful enough to find root cause Sean Mullan
  • Re: RFR: 8286444: javac errors after JDK-8251329 are not helpful enough to find root cause Sean Mullan
  • Re: RFR: 8286444: javac errors after JDK-8251329 are not helpful enough to find root cause Alan Bateman
  • Re: RFR: 8286444: javac errors after JDK-8251329 are not helpful enough to find root cause Sean Mullan
  • Re: RFR: 8286444: javac errors after JDK-8251329 are not helpful enough to find root cause Lance Andersen
  • Re: RFR: 8286444: javac errors after JDK-8251329 are not helpful enough to find root cause Martin Doerr
• HttpClient has no explicit way of releasing threads Rafael Winterhalter
  • Re: HttpClient has no explicit way of releasing threads Daniel Fuchs
  • Re: HttpClient has no explicit way of releasing threads Rafael Winterhalter
  • Re: HttpClient has no explicit way of releasing threads Remi Forax
  • Re: HttpClient has no explicit way of releasing threads Daniel Fuchs
  • Re: HttpClient has no explicit way of releasing threads Rafael Winterhalter
  • Re: HttpClient has no explicit way of releasing threads Cay Horstmann
• RFR: 8282351: jpackage does not work if class file has `$$` in the name on windows Alexey Semenyuk
  • Re: RFR: 8282351: jpackage does not work if class file has `$$` in the name on windows Alexander Matveev
  • Integrated: 8282351: jpackage does not work if class file has `$$` in the name on windows Alexey Semenyuk
• RFR: 8286438: Add jhsdb jstack processing without --mixed in efh Leonid Mesnik
• RFR: 8285844: TimeZone.getTimeZone(ZoneOffset) does not work for all ZoneOffsets and returns GMT unexpected Naoto Sato
  • Re: RFR: 8285844: TimeZone.getTimeZone(ZoneOffset) does not work for all ZoneOffsets and returns GMT unexpected Uwe Schindler
  • Re: RFR: 8285844: TimeZone.getTimeZone(ZoneOffset) does not work for all ZoneOffsets and returns GMT unexpected [v2] Naoto Sato
  • Re: RFR: 8285844: TimeZone.getTimeZone(ZoneOffset) does not work for all ZoneOffsets and returns GMT unexpected [v2] Stephen Colebourne
  • Re: RFR: 8285844: TimeZone.getTimeZone(ZoneOffset) does not work for all ZoneOffsets and returns GMT unexpected [v2] Uwe Schindler
  • Re: RFR: 8285844: TimeZone.getTimeZone(ZoneOffset) does not work for all ZoneOffsets and returns GMT unexpected [v2] Uwe Schindler
  • Re: RFR: 8285844: TimeZone.getTimeZone(ZoneOffset) does not work for all ZoneOffsets and returns GMT unexpected [v3] Naoto Sato
  • Re: RFR: 8285844: TimeZone.getTimeZone(ZoneOffset) does not work for all ZoneOffsets and returns GMT unexpected Jaikiran Pai
  • Re: RFR: 8285844: TimeZone.getTimeZone(ZoneOffset) does not work for all ZoneOffsets and returns GMT unexpected [v2] Naoto Sato
  • Re: RFR: 8285844: TimeZone.getTimeZone(ZoneOffset) does not work for all ZoneOffsets and returns GMT unexpected [v2] Uwe Schindler
  • Re: RFR: 8285844: TimeZone.getTimeZone(ZoneOffset) does not work for all ZoneOffsets and returns GMT unexpected Jaikiran Pai
  • Re: RFR: 8285844: TimeZone.getTimeZone(ZoneOffset) does not work for all ZoneOffsets and returns GMT unexpected [v2] Naoto Sato
  • Re: RFR: 8285844: TimeZone.getTimeZone(ZoneOffset) does not work for all ZoneOffsets and returns GMT unexpected [v3] Naoto Sato
  • Re: RFR: 8285844: TimeZone.getTimeZone(ZoneOffset) does not work for all ZoneOffsets and returns GMT unexpected [v4] Naoto Sato
  • Re: RFR: 8285844: TimeZone.getTimeZone(ZoneOffset) does not work for all ZoneOffsets and returns GMT unexpected [v4] Joe Wang
  • Re: RFR: 8285844: TimeZone.getTimeZone(ZoneOffset) does not work for all ZoneOffsets and returns GMT unexpected [v4] Naoto Sato
  • Re: RFR: 8285844: TimeZone.getTimeZone(ZoneOffset) does not work for all ZoneOffsets and returns GMT unexpected [v5] Naoto Sato
  • Re: RFR: 8285844: TimeZone.getTimeZone(ZoneOffset) does not work for all ZoneOffsets and returns GMT unexpected [v5] Stephen Colebourne
  • Re: RFR: 8285844: TimeZone.getTimeZone(ZoneOffset) does not work for all ZoneOffsets and returns GMT unexpected [v5] Joe Wang
  • Re: RFR: 8285844: TimeZone.getTimeZone(ZoneOffset) does not work for all ZoneOffsets and returns GMT unexpected [v5] Uwe Schindler
  • Integrated: 8285844: TimeZone.getTimeZone(ZoneOffset) does not work for all ZoneOffsets and returns GMT unexpected Naoto Sato
• Re: RFR: 8280035: Use Class.isInstance instead of Class.isAssignableFrom where applicable [v2] Phil Race
  • Re: RFR: 8280035: Use Class.isInstance instead of Class.isAssignableFrom where applicable [v2] Daniel Fuchs
  • Re: RFR: 8280035: Use Class.isInstance instead of Class.isAssignableFrom where applicable [v2] Andrey Turbanov
  • Re: RFR: 8280035: Use Class.isInstance instead of Class.isAssignableFrom where applicable [v2] Daniel Fuchs
  • Re: RFR: 8280035: Use Class.isInstance instead of Class.isAssignableFrom where applicable [v2] Andrey Turbanov
  • Re: RFR: 8280035: Use Class.isInstance instead of Class.isAssignableFrom where applicable [v2] Roger Riggs
  • Re: RFR: 8280035: Use Class.isInstance instead of Class.isAssignableFrom where applicable [v2] Andrey Turbanov
• RFR: 8286368: Cleanup problem lists after loom integration Leonid Mesnik
  • Re: RFR: 8286368: Cleanup problem lists after loom integration Alan Bateman
  • Re: RFR: 8286368: Cleanup problem lists after loom integration [v2] Leonid Mesnik
  • Re: RFR: 8286368: Cleanup problem lists after loom integration [v2] David Holmes
  • Re: RFR: 8286368: Cleanup problem lists after loom integration [v2] Leonid Mesnik
  • Re: RFR: 8286368: Cleanup problem lists after loom integration [v2] David Holmes
  • Integrated: 8286368: Cleanup problem lists after loom integration Leonid Mesnik
• RFR: 8284980: Test vmTestbase/nsk/stress/except/except010.java times out with -Xcomp -XX:+DeoptimizeALot Leonid Mesnik
  • Re: RFR: 8284980: Test vmTestbase/nsk/stress/except/except010.java times out with -Xcomp -XX:+DeoptimizeALot [v2] Leonid Mesnik
• Re: RFR: 8282191: Implementation of Foreign Function & Memory API (Preview) [v43] Maurizio Cimadamore
  • Re: RFR: 8282191: Implementation of Foreign Function & Memory API (Preview) [v43] ExE Boss
  • Re: RFR: 8282191: Implementation of Foreign Function & Memory API (Preview) [v43] Maurizio Cimadamore
• RFR: 8244681: Add a warning for possibly lossy conversion in compound assignments Adam Sotona
  • Re: RFR: 8244681: Add a warning for possibly lossy conversion in compound assignments Erik Joelsson
  • Re: RFR: 8244681: Add a warning for possibly lossy conversion in compound assignments Phil Race
  • Re: RFR: 8244681: Add a warning for possibly lossy conversion in compound assignments Joe Darcy
  • Re: RFR: 8244681: Add a warning for possibly lossy conversion in compound assignments Adam Sotona
  • Re: RFR: 8244681: Add a warning for possibly lossy conversion in compound assignments [v2] Adam Sotona
  • Re: RFR: 8244681: Add a warning for possibly lossy conversion in compound assignments [v2] John R Rose
  • Re: RFR: 8244681: Add a warning for possibly lossy conversion in compound assignments [v3] Adam Sotona

• Earlier messages
• Later messages