Re: RFR: 8315884: New Object to ObjectMonitor mapping [v15]

2024-08-13 Thread Axel Boldt-Christmas
On Tue, 13 Aug 2024 17:05:38 GMT, Daniel D. Daugherty wrote: >> Axel Boldt-Christmas has updated the pull request incrementally with two >> additional commits since the last revision: >> >> - Remove the last OMWorld references >> - Rename omworldtable_work to object_monitor_table_work > > sr

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v15]

2024-08-13 Thread Axel Boldt-Christmas
On Tue, 13 Aug 2024 16:34:17 GMT, Daniel D. Daugherty wrote: >> Axel Boldt-Christmas has updated the pull request incrementally with two >> additional commits since the last revision: >> >> - Remove the last OMWorld references >> - Rename omworldtable_work to object_monitor_table_work > > sr

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v11]

2024-08-13 Thread Axel Boldt-Christmas
On Mon, 12 Aug 2024 22:40:06 GMT, Daniel D. Daugherty wrote: >> Axel Boldt-Christmas has updated the pull request incrementally with one >> additional commit since the last revision: >> >> Missing DEBUG_ONLY > > src/hotspot/share/interpreter/zero/bytecodeInterpreter.cpp line 632: > >> 630:

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v17]

2024-08-13 Thread Axel Boldt-Christmas
> When inflating a monitor the `ObjectMonitor*` is written directly over the > `markWord` and any overwritten data is displaced into a displaced `markWord`. > This is problematic for concurrent GCs which needs extra care or looser > semantics to use this displaced data. In Lilliput this data als

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v16]

2024-08-13 Thread David Holmes
On Tue, 13 Aug 2024 16:30:12 GMT, Axel Boldt-Christmas wrote: >> When inflating a monitor the `ObjectMonitor*` is written directly over the >> `markWord` and any overwritten data is displaced into a displaced >> `markWord`. This is problematic for concurrent GCs which needs extra care or >> l

Re: RFR: 8338021: Support saturating vector operators in VectorAPI [v3]

2024-08-13 Thread Jatin Bhateja
> Hi All, > > As per the discussion on panama-dev mailing list[1], patch adds the support > following new vector operators. > > > . SATURATING_UADD : Saturating unsigned addition. > . SATURATING_ADD: Saturating signed addition. > . SATURATING_USUB : Saturating unsigned

Re: RFR: 8322420: [Linux] cgroup v2: Limits in parent nested control groups are not detected [v19]

2024-08-13 Thread Jan Kratochvil
On Mon, 12 Aug 2024 18:39:46 GMT, Severin Gehwolf wrote: >> Jan Kratochvil has updated the pull request incrementally with two >> additional commits since the last revision: >> >> - Inline adjust_controller() twice >> - Revert "Unify 4 copies of adjust_controller()" >> >>This reverts

Re: RFR: 8322420: [Linux] cgroup v2: Limits in parent nested control groups are not detected [v20]

2024-08-13 Thread Jan Kratochvil
> The testcase requires root permissions. > > Fix by Severin Gehwolf. > Testcase by Jan Kratochvil. Jan Kratochvil has updated the pull request incrementally with one additional commit since the last revision: Testcase update upon review by Severin Gehwolf - Changes: - all: h

Re: compatibility impact of JDK-8325621 (Improve jspawnhelper version checks)

2024-08-13 Thread Man Cao
HI, In addition to Liam's point, I'd like to point out: 1. The version check in jspawnhelper is for the full JDK version. This means any future in-place JDK update could trigger this problem for long-running applications. 2. Typical Linux package managers (e.g. apt, yum) seem to update the JDK pa

Re: RFR: 8337302: Undefined type variable results in null [v4]

2024-08-13 Thread Chen Liang
On Tue, 13 Aug 2024 23:41:06 GMT, Rafael Winterhalter wrote: >> When a type uses a type variable without a declaration, no exception is >> thrown. This change triggers a `TypeNotFoundException` to be thrown. > > Rafael Winterhalter has updated the pull request incrementally with one > addition

Re: RFR: 8337302: Undefined type variable results in null [v4]

2024-08-13 Thread Rafael Winterhalter
> When a type uses a type variable without a declaration, no exception is > thrown. This change triggers a `TypeNotFoundException` to be thrown. Rafael Winterhalter has updated the pull request incrementally with one additional commit since the last revision: 8337302: Fix copyright years. --

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v16]

2024-08-13 Thread Daniel D . Daugherty
On Tue, 13 Aug 2024 16:30:12 GMT, Axel Boldt-Christmas wrote: >> When inflating a monitor the `ObjectMonitor*` is written directly over the >> `markWord` and any overwritten data is displaced into a displaced >> `markWord`. This is problematic for concurrent GCs which needs extra care or >> l

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v15]

2024-08-13 Thread Daniel D . Daugherty
On Tue, 13 Aug 2024 16:49:42 GMT, Daniel D. Daugherty wrote: >> Axel Boldt-Christmas has updated the pull request incrementally with two >> additional commits since the last revision: >> >> - Remove the last OMWorld references >> - Rename omworldtable_work to object_monitor_table_work > > sr

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v16]

2024-08-13 Thread Daniel D . Daugherty
On Tue, 13 Aug 2024 16:30:12 GMT, Axel Boldt-Christmas wrote: >> When inflating a monitor the `ObjectMonitor*` is written directly over the >> `markWord` and any overwritten data is displaced into a displaced >> `markWord`. This is problematic for concurrent GCs which needs extra care or >> l

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v15]

2024-08-13 Thread Daniel D . Daugherty
On Tue, 13 Aug 2024 14:56:32 GMT, Coleen Phillimore wrote: >> Axel Boldt-Christmas has updated the pull request incrementally with two >> additional commits since the last revision: >> >> - Remove the last OMWorld references >> - Rename omworldtable_work to object_monitor_table_work > > src/h

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v6]

2024-08-13 Thread Daniel D . Daugherty
On Mon, 15 Jul 2024 00:45:10 GMT, Axel Boldt-Christmas wrote: >> src/hotspot/share/runtime/lightweightSynchronizer.cpp line 401: >> >>> 399: >>> 400: if (inserted) { >>> 401: // Hopefully the performance counters are allocated on distinct >> >> It doesn't look like the counters are on d

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v15]

2024-08-13 Thread Daniel D . Daugherty
On Tue, 13 Aug 2024 14:52:03 GMT, Axel Boldt-Christmas wrote: >> When inflating a monitor the `ObjectMonitor*` is written directly over the >> `markWord` and any overwritten data is displaced into a displaced >> `markWord`. This is problematic for concurrent GCs which needs extra care or >> l

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v11]

2024-08-13 Thread Daniel D . Daugherty
On Mon, 12 Aug 2024 15:58:14 GMT, Axel Boldt-Christmas wrote: >> When inflating a monitor the `ObjectMonitor*` is written directly over the >> `markWord` and any overwritten data is displaced into a displaced >> `markWord`. This is problematic for concurrent GCs which needs extra care or >> l

Re: RFR: 8336384: AbstractQueuedSynchronizer.acquire should cancel acquire when failing due to a LinkageError or other errors [v2]

2024-08-13 Thread David Holmes
On Tue, 13 Aug 2024 08:02:04 GMT, Alan Bateman wrote: > > It has been a while since I knew this code reasonably well so perhaps I > > have just forgotten this difference between AQS and built-in monitors, but > > it seems that a Condition.await can return by throwing an exception without > > r

Re: RFR: 8338014: Improve usage of @jvms tags in class file API [v2]

2024-08-13 Thread Chen Liang
On Tue, 13 Aug 2024 14:37:32 GMT, Sonia Zaldana Calles wrote: >> Hi all, >> >> This PR addresses [8338014](https://bugs.openjdk.org/browse/JDK-8338014) >> improving the use of `@jvms` tags by adding `JVMS` prior to the tag. >> >> Thanks, >> Sonia > > Sonia Zaldana Calles has updated the pu

Re: RFR: 8338014: Improve usage of @jvms tags in class file API [v2]

2024-08-13 Thread Joe Darcy
On Tue, 13 Aug 2024 14:37:32 GMT, Sonia Zaldana Calles wrote: >> Hi all, >> >> This PR addresses [8338014](https://bugs.openjdk.org/browse/JDK-8338014) >> improving the use of `@jvms` tags by adding `JVMS` prior to the tag. >> >> Thanks, >> Sonia > > Sonia Zaldana Calles has updated the pu

Re: RFR: 8338014: Improve usage of @jvms tags in class file API [v2]

2024-08-13 Thread Sonia Zaldana Calles
On Mon, 12 Aug 2024 18:55:47 GMT, Joe Darcy wrote: >> Looks fine; increasing review count to also include someone who more >> directly maintains this API. >> >> If you haven't done so already, I recommend also doing a quick check for an >> analagous issue with `@jls` tags in this API. > >> @jd

Re: RFR: 8336754: Remodel TypeAnnotation to "has" instead of "be" an Annotation [v10]

2024-08-13 Thread Chen Liang
> `TypeAnnotation` is not an annotation, as it should not be used in places > like `AnnotationValue.ofAnnotation`. Thus it's remodeled to contain an > annotation at a given location instead of to be an annotation. > > Depends on #20205. Chen Liang has updated the pull request incrementally with

Re: RFR: 8336754: Remodel TypeAnnotation to "has" instead of "be" an Annotation [v9]

2024-08-13 Thread Chen Liang
> `TypeAnnotation` is not an annotation, as it should not be used in places > like `AnnotationValue.ofAnnotation`. Thus it's remodeled to contain an > annotation at a given location instead of to be an annotation. > > Depends on #20205. Chen Liang has updated the pull request with a new target

Withdrawn: 8261400: Reflection member filtering registration might be flawed

2024-08-13 Thread Chen Liang
On Fri, 5 Jul 2024 19:27:27 GMT, Chen Liang wrote: > Please review this patch that address the reflection member filtering flaws. > > 1. Remove a pointless bootstrap check to ensure no filter is accidentally > bypassed due to class-loading order. > 2. Clarify the scenarios for filtering, and th

Re: RFR: 8337302: Undefined type variable results in null [v3]

2024-08-13 Thread Chen Liang
On Mon, 12 Aug 2024 23:08:07 GMT, Rafael Winterhalter wrote: >> When a type uses a type variable without a declaration, no exception is >> thrown. This change triggers a `TypeNotFoundException` to be thrown. > > Rafael Winterhalter has updated the pull request incrementally with one > addition

Re: RFR: 8336856: Efficient hidden class-based string concatenation strategy [v55]

2024-08-13 Thread Claes Redestad
On Tue, 13 Aug 2024 16:34:18 GMT, Shaojin Wen wrote: >> This PR implements the same algorithm as the current generateMHInlineCopy >> based on bytecode to improve startup performance. > > Shaojin Wen has updated the pull request incrementally with two additional > commits since the last revision

Re: RFR: 8332842: Optimize empty CopyOnWriteArrayList allocations [v3]

2024-08-13 Thread jengebr
On Wed, 19 Jun 2024 12:52:46 GMT, Alan Bateman wrote: >> @AlanBateman -- could you please take a look? Thanks. > >> @AlanBateman -- could you please take a look? Thanks. > > There was a lot of heap analysis done a few years ago that shined a light on > the number of empty collections in a typic

compatibility impact of JDK-8325621 (Improve jspawnhelper version checks)

2024-08-13 Thread Liam Miller-Cushon
Hi, I have a data point to share on the compatibility impact of JDK-8325621 (Improve jspawnhelper version checks), which was backported to earlier release trains. As a result of that change, doing an in-place upgrade from 22.0.1 to 22.0.2 breaks long-running Java applications that create subproce

Re: RFR: 8336856: Efficient hidden class-based string concatenation strategy [v55]

2024-08-13 Thread Shaojin Wen
> This PR implements the same algorithm as the current generateMHInlineCopy > based on bytecode to improve startup performance. Shaojin Wen has updated the pull request incrementally with two additional commits since the last revision: - static final - code style - Changes: -

Re: Stream Gatherers (JEP 473) feedback

2024-08-13 Thread Anthony Vanelverdinghe
Hi Viktor Your previous response inspired me to experiment some more with Gatherers As a result I'd like to make a couple propositions: * add an additional type parameter. After doing so, type inference no longer needs any assistance: `var maxGatherer = Gatherer.ofSequential(State::new, State

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v16]

2024-08-13 Thread Axel Boldt-Christmas
> When inflating a monitor the `ObjectMonitor*` is written directly over the > `markWord` and any overwritten data is displaced into a displaced `markWord`. > This is problematic for concurrent GCs which needs extra care or looser > semantics to use this displaced data. In Lilliput this data als

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v9]

2024-08-13 Thread Roman Kennke
On Tue, 13 Aug 2024 12:57:23 GMT, Axel Boldt-Christmas wrote: >> src/hotspot/cpu/x86/c2_MacroAssembler_x86.cpp line 674: >> >>> 672: >>> 673: // Search for obj in cache. >>> 674: bind(loop); >> >> Same loop transformation would be possible here. > > I tried the following (see diff

Re: RFR: 8338014: Improve usage of @jvms tags in class file API [v2]

2024-08-13 Thread Chen Liang
On Tue, 13 Aug 2024 14:37:32 GMT, Sonia Zaldana Calles wrote: >> Hi all, >> >> This PR addresses [8338014](https://bugs.openjdk.org/browse/JDK-8338014) >> improving the use of `@jvms` tags by adding `JVMS` prior to the tag. >> >> Thanks, >> Sonia > > Sonia Zaldana Calles has updated the pu

Integrated: 8335927: Revisit AnnotationConstantValueEntry and AnnotationValue.OfConstant

2024-08-13 Thread Chen Liang
On Fri, 2 Aug 2024 00:39:12 GMT, Chen Liang wrote: > 1. Add notes and docs about the difference between resolved constants and > constant pool descriptors for annotation constants (e.g. `char` vs > `IntegerEntry`) > 2. Improved value specification to specify their tags. > 3. Improved value fact

Re: RFR: 8335927: Revisit AnnotationConstantValueEntry and AnnotationValue.OfConstant [v5]

2024-08-13 Thread Chen Liang
On Fri, 2 Aug 2024 16:31:48 GMT, Chen Liang wrote: >> 1. Add notes and docs about the difference between resolved constants and >> constant pool descriptors for annotation constants (e.g. `char` vs >> `IntegerEntry`) >> 2. Improved value specification to specify their tags. >> 3. Improved value

Re: RFR: 8336856: Efficient hidden class-based string concatenation strategy [v54]

2024-08-13 Thread Claes Redestad
On Tue, 13 Aug 2024 09:38:31 GMT, Shaojin Wen wrote: >> This PR implements the same algorithm as the current generateMHInlineCopy >> based on bytecode to improve startup performance. > > Shaojin Wen has updated the pull request incrementally with two additional > commits since the last revision

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v15]

2024-08-13 Thread Coleen Phillimore
On Tue, 13 Aug 2024 14:52:03 GMT, Axel Boldt-Christmas wrote: >> When inflating a monitor the `ObjectMonitor*` is written directly over the >> `markWord` and any overwritten data is displaced into a displaced >> `markWord`. This is problematic for concurrent GCs which needs extra care or >> l

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v9]

2024-08-13 Thread Coleen Phillimore
On Mon, 12 Aug 2024 14:37:50 GMT, Axel Boldt-Christmas wrote: >> This is a really good suggestion and might help a lot with the performance >> problems that we see with the table with heavily contended locking. I think >> we should change this in a follow-on patch (which I'll work on). > > I

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v11]

2024-08-13 Thread Axel Boldt-Christmas
On Mon, 12 Aug 2024 18:55:41 GMT, Coleen Phillimore wrote: >> Axel Boldt-Christmas has updated the pull request incrementally with one >> additional commit since the last revision: >> >> Missing DEBUG_ONLY > > src/hotspot/share/runtime/lightweightSynchronizer.cpp line 341: > >> 339: }; >> 34

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v15]

2024-08-13 Thread Axel Boldt-Christmas
> When inflating a monitor the `ObjectMonitor*` is written directly over the > `markWord` and any overwritten data is displaced into a displaced `markWord`. > This is problematic for concurrent GCs which needs extra care or looser > semantics to use this displaced data. In Lilliput this data als

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v14]

2024-08-13 Thread Axel Boldt-Christmas
> When inflating a monitor the `ObjectMonitor*` is written directly over the > `markWord` and any overwritten data is displaced into a displaced `markWord`. > This is problematic for concurrent GCs which needs extra care or looser > semantics to use this displaced data. In Lilliput this data als

Re: RFR: 8338014: Improve usage of @jvms tags in class file API [v2]

2024-08-13 Thread Sonia Zaldana Calles
> Hi all, > > This PR addresses [8338014](https://bugs.openjdk.org/browse/JDK-8338014) > improving the use of `@jvms` tags by adding `JVMS` prior to the tag. > > Thanks, > Sonia Sonia Zaldana Calles has updated the pull request incrementally with two additional commits since the last revisi

Re: RFR: 8338146: Improve Exchanger performance with VirtualThreads

2024-08-13 Thread Doug Lea
On Tue, 13 Aug 2024 11:52:05 GMT, Viktor Klang wrote: >> The Exchanger class uses spin-waits that are hostile to some uses of >> VirtualThreads. Improving this requires a means of estimating whether there >> are many VirtualThreads with few carriers, which can be supported by adding >> a metho

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v13]

2024-08-13 Thread Axel Boldt-Christmas
> When inflating a monitor the `ObjectMonitor*` is written directly over the > `markWord` and any overwritten data is displaced into a displaced `markWord`. > This is problematic for concurrent GCs which needs extra care or looser > semantics to use this displaced data. In Lilliput this data als

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v9]

2024-08-13 Thread Axel Boldt-Christmas
On Tue, 23 Jul 2024 14:27:34 GMT, Coleen Phillimore wrote: >> src/hotspot/share/runtime/lightweightSynchronizer.cpp line 105: >> >>> 103: }; >>> 104: >>> 105: class LookupMonitor : public StackObj { >> >> I'm not understanding why we need this little wrapper class. > > It's a two way looku

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v9]

2024-08-13 Thread Axel Boldt-Christmas
On Tue, 23 Jul 2024 16:36:18 GMT, Coleen Phillimore wrote: >> src/hotspot/share/runtime/lightweightSynchronizer.cpp line 102: >> >>> 100: assert(*value != nullptr, "must be"); >>> 101: return (*value)->object_is_cleared(); >>> 102: } >> >> The `is_dead` functions seem oddly plac

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v9]

2024-08-13 Thread Axel Boldt-Christmas
On Tue, 23 Jul 2024 13:19:02 GMT, Coleen Phillimore wrote: >> src/hotspot/share/runtime/lightweightSynchronizer.cpp line 62: >> >>> 60: class ObjectMonitorWorld : public CHeapObj { >>> 61: struct Config { >>> 62: using Value = ObjectMonitor*; >> >> Does this alias really help? We don't st

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v9]

2024-08-13 Thread Axel Boldt-Christmas
On Tue, 23 Jul 2024 20:21:05 GMT, Coleen Phillimore wrote: >> Only legacy locking uses the displaced header, I believe, which isn't clear >> in this code at all. This seems like a fix. We should probably assert that >> only legacy locking uses this field as a displaced header. > > Update: yes

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v12]

2024-08-13 Thread Axel Boldt-Christmas
> When inflating a monitor the `ObjectMonitor*` is written directly over the > `markWord` and any overwritten data is displaced into a displaced `markWord`. > This is problematic for concurrent GCs which needs extra care or looser > semantics to use this displaced data. In Lilliput this data als

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v6]

2024-08-13 Thread Axel Boldt-Christmas
On Fri, 12 Jul 2024 15:32:45 GMT, Roman Kennke wrote: >> Axel Boldt-Christmas has updated the pull request incrementally with one >> additional commit since the last revision: >> >> Update arguments.cpp > > src/hotspot/share/runtime/lightweightSynchronizer.cpp line 58: > >> 56: >> 57: // >>

Re: RFR: 8315884: New Object to ObjectMonitor mapping [v9]

2024-08-13 Thread Axel Boldt-Christmas
On Tue, 16 Jul 2024 12:36:08 GMT, Roman Kennke wrote: >> Axel Boldt-Christmas has updated the pull request incrementally with 10 >> additional commits since the last revision: >> >> - Remove try_read >> - Add explicit to single parameter constructors >> - Remove superfluous access specifier

Re: RFR: 8338146: Improve Exchanger performance with VirtualThreads

2024-08-13 Thread Viktor Klang
On Mon, 12 Aug 2024 17:07:42 GMT, Doug Lea wrote: > The Exchanger class uses spin-waits that are hostile to some uses of > VirtualThreads. Improving this requires a means of estimating whether there > are many VirtualThreads with few carriers, which can be supported by adding a > method in cla

Integrated: 8336384: AbstractQueuedSynchronizer.acquire should cancel acquire when failing due to a LinkageError or other errors

2024-08-13 Thread Viktor Klang
On Mon, 12 Aug 2024 13:41:24 GMT, Viktor Klang wrote: > 8336384: AbstractQueuedSynchronizer.acquire should cancel acquire when > failing due to a LinkageError or other errors This pull request has now been integrated. Changeset: fbe4cc96 Author:Viktor Klang URL: https://git.openjdk

Re: RFR: 8336856: Efficient hidden class-based string concatenation strategy [v54]

2024-08-13 Thread Shaojin Wen
> This PR implements the same algorithm as the current generateMHInlineCopy > based on bytecode to improve startup performance. Shaojin Wen has updated the pull request incrementally with two additional commits since the last revision: - remove unused - Minor refactoring - Chang

Re: RFR: 8336856: Efficient hidden class-based string concatenation strategy [v51]

2024-08-13 Thread Claes Redestad
On Tue, 13 Aug 2024 09:00:10 GMT, Shaojin Wen wrote: >> This PR implements the same algorithm as the current generateMHInlineCopy >> based on bytecode to improve startup performance. > > Shaojin Wen has updated the pull request incrementally with one additional > commit since the last revision:

Re: RFR: 8336856: Efficient hidden class-based string concatenation strategy [v53]

2024-08-13 Thread Shaojin Wen
> This PR implements the same algorithm as the current generateMHInlineCopy > based on bytecode to improve startup performance. Shaojin Wen has updated the pull request incrementally with one additional commit since the last revision: Minor refactoring - Changes: - all: https:

Re: RFR: 8336856: Efficient hidden class-based string concatenation strategy [v51]

2024-08-13 Thread Claes Redestad
On Tue, 13 Aug 2024 09:00:10 GMT, Shaojin Wen wrote: >> This PR implements the same algorithm as the current generateMHInlineCopy >> based on bytecode to improve startup performance. > > Shaojin Wen has updated the pull request incrementally with one additional > commit since the last revision:

Re: RFR: 8336856: Efficient hidden class-based string concatenation strategy [v52]

2024-08-13 Thread Shaojin Wen
> This PR implements the same algorithm as the current generateMHInlineCopy > based on bytecode to improve startup performance. Shaojin Wen has updated the pull request incrementally with one additional commit since the last revision: Simplify HiddenClassUnloading - Changes: -

Re: RFR: 8336856: Efficient hidden class-based string concatenation strategy [v48]

2024-08-13 Thread Shaojin Wen
On Tue, 13 Aug 2024 08:04:07 GMT, Claes Redestad wrote: >> Shaojin Wen has updated the pull request incrementally with one additional >> commit since the last revision: >> >> add jtreg HiddenClassUnloading > > test/jdk/java/lang/String/concat/HiddenClassUnloading.java line 67: > >> 65:

Re: RFR: 8336856: Efficient hidden class-based string concatenation strategy [v51]

2024-08-13 Thread Shaojin Wen
> This PR implements the same algorithm as the current generateMHInlineCopy > based on bytecode to improve startup performance. Shaojin Wen has updated the pull request incrementally with one additional commit since the last revision: Update src/java.base/share/classes/java/lang/invoke/String

Re: RFR: 8336856: Efficient hidden class-based string concatenation strategy [v50]

2024-08-13 Thread Shaojin Wen
> This PR implements the same algorithm as the current generateMHInlineCopy > based on bytecode to improve startup performance. Shaojin Wen has updated the pull request incrementally with three additional commits since the last revision: - Simplify HiddenClassUnloading - Remove unnecessary lo

Re: RFR: 8336856: Efficient hidden class-based string concatenation strategy [v49]

2024-08-13 Thread Claes Redestad
On Tue, 13 Aug 2024 08:36:18 GMT, Shaojin Wen wrote: >> This PR implements the same algorithm as the current generateMHInlineCopy >> based on bytecode to improve startup performance. > > Shaojin Wen has updated the pull request incrementally with four additional > commits since the last revisio

Re: RFR: 8336856: Efficient hidden class-based string concatenation strategy [v49]

2024-08-13 Thread Shaojin Wen
> This PR implements the same algorithm as the current generateMHInlineCopy > based on bytecode to improve startup performance. Shaojin Wen has updated the pull request incrementally with four additional commits since the last revision: - Update src/java.base/share/classes/java/lang/invoke/Str

Re: RFR: 8336856: Efficient hidden class-based string concatenation strategy [v48]

2024-08-13 Thread Claes Redestad
On Tue, 13 Aug 2024 01:39:33 GMT, Shaojin Wen wrote: >> This PR implements the same algorithm as the current generateMHInlineCopy >> based on bytecode to improve startup performance. > > Shaojin Wen has updated the pull request incrementally with one additional > commit since the last revision:

Re: RFR: 8336384: AbstractQueuedSynchronizer.acquire should cancel acquire when failing due to a LinkageError or other errors [v2]

2024-08-13 Thread Alan Bateman
On Mon, 12 Aug 2024 23:39:02 GMT, David Holmes wrote: > It has been a while since I knew this code reasonably well so perhaps I have > just forgotten this difference between AQS and built-in monitors, but it > seems that a Condition.await can return by throwing an exception without > re-acquir

Re: RFR: 8336384: AbstractQueuedSynchronizer.acquire should cancel acquire when failing due to a LinkageError or other errors [v2]

2024-08-13 Thread Alan Bateman
On Mon, 12 Aug 2024 23:28:26 GMT, David Holmes wrote: > Though I'm unclear how that compiles without the method declaring `throws > Throwable` ?? It wouldn't need that because of precise rethrow. In any case, having Error and RuntimeException are okay. - PR Review Comment: https:

Re: RFR: 8336384: AbstractQueuedSynchronizer.acquire should cancel acquire when failing due to a LinkageError or other errors [v2]

2024-08-13 Thread Alan Bateman
On Mon, 12 Aug 2024 16:11:46 GMT, Viktor Klang wrote: >> 8336384: AbstractQueuedSynchronizer.acquire should cancel acquire when >> failing due to a LinkageError or other errors > > Viktor Klang has updated the pull request incrementally with one additional > commit since the last revision: > >