On Fri, 24 Jan 2025 20:22:07 GMT, Chris Plummer wrote:
>> If you run hotspot with -XX:+DeoptimizeObjectsALot, it will create one or
>> more DeoptimizeObjectsALotThread threads. This is one of many JavaThread
>> subclasses that SA needs to know about, but in this case it does not. When
>> SA tr
On Fri, 24 Jan 2025 23:23:43 GMT, Chris Plummer wrote:
> I don't see how that relates to this change. It sounds more like a general
> suggestion to overhaul of how vmStructs is implemented.
It relates because if something like that was available then we could register
types that are local to a
On Fri, 24 Jan 2025 22:52:19 GMT, Dean Long wrote:
> > > Overall the changes seem fine, however it would be nice if the
> > > vmStructs.cpp registration mechanism was modular and extensible, instead
> > > of monolithic. That would make it easier to register private types, or
> > > even types o
On Fri, 24 Jan 2025 20:22:07 GMT, Chris Plummer wrote:
>> If you run hotspot with -XX:+DeoptimizeObjectsALot, it will create one or
>> more DeoptimizeObjectsALotThread threads. This is one of many JavaThread
>> subclasses that SA needs to know about, but in this case it does not. When
>> SA tr
On Thu, 23 Jan 2025 22:30:48 GMT, Chris Plummer wrote:
> > Overall the changes seem fine, however it would be nice if the
> > vmStructs.cpp registration mechanism was modular and extensible, instead of
> > monolithic. That would make it easier to register private types, or even
> > types outsi
On Fri, 24 Jan 2025 20:13:29 GMT, Chris Plummer wrote:
>> src/jdk.hotspot.agent/share/classes/sun/jvm/hotspot/runtime/Threads.java
>> line 168:
>>
>>> 166: JvmtiAgentThread, NotificationThread, MonitorDeflationThread,
>>> 167: StringDedupThread, AttachListenerThread,
>>> Deoptimize
> If you run hotspot with -XX:+DeoptimizeObjectsALot, it will create one or
> more DeoptimizeObjectsALotThread threads. This is one of many JavaThread
> subclasses that SA needs to know about, but in this case it does not. When SA
> tries to create a mirror of one of these threads, it fails with
On Fri, 24 Jan 2025 10:19:30 GMT, Kevin Walls wrote:
>> If you run hotspot with -XX:+DeoptimizeObjectsALot, it will create one or
>> more DeoptimizeObjectsALotThread threads. This is one of many JavaThread
>> subclasses that SA needs to know about, but in this case it does not. When
>> SA trie
On Thu, 23 Jan 2025 20:15:35 GMT, Chris Plummer wrote:
> If you run hotspot with -XX:+DeoptimizeObjectsALot, it will create one or
> more DeoptimizeObjectsALotThread threads. This is one of many JavaThread
> subclasses that SA needs to know about, but in this case it does not. When SA
> tries
On Thu, 23 Jan 2025 20:15:35 GMT, Chris Plummer wrote:
> If you run hotspot with -XX:+DeoptimizeObjectsALot, it will create one or
> more DeoptimizeObjectsALotThread threads. This is one of many JavaThread
> subclasses that SA needs to know about, but in this case it does not. When SA
> tries
On Thu, 23 Jan 2025 20:15:35 GMT, Chris Plummer wrote:
> If you run hotspot with -XX:+DeoptimizeObjectsALot, it will create one or
> more DeoptimizeObjectsALotThread threads. This is one of many JavaThread
> subclasses that SA needs to know about, but in this case it does not. When SA
> tries
On Thu, 23 Jan 2025 20:15:35 GMT, Chris Plummer wrote:
> If you run hotspot with -XX:+DeoptimizeObjectsALot, it will create one or
> more DeoptimizeObjectsALotThread threads. This is one of many JavaThread
> subclasses that SA needs to know about, but in this case it does not. When SA
> tries
On Thu, 23 Jan 2025 22:03:45 GMT, Dean Long wrote:
> Overall the changes seem fine, however it would be nice if the vmStructs.cpp
> registration mechanism was modular and extensible, instead of monolithic.
> That would make it easier to register private types, or even types outside of
> libjvm
On Thu, 23 Jan 2025 20:15:35 GMT, Chris Plummer wrote:
> If you run hotspot with -XX:+DeoptimizeObjectsALot, it will create one or
> more DeoptimizeObjectsALotThread threads. This is one of many JavaThread
> subclasses that SA needs to know about, but in this case it does not. When SA
> tries
On Thu, 23 Jan 2025 20:15:35 GMT, Chris Plummer wrote:
> If you run hotspot with -XX:+DeoptimizeObjectsALot, it will create one or
> more DeoptimizeObjectsALotThread threads. This is one of many JavaThread
> subclasses that SA needs to know about, but in this case it does not. When SA
> tries
If you run hotspot with -XX:+DeoptimizeObjectsALot, it will create one or more
DeoptimizeObjectsALotThread threads. This is one of many JavaThread subclasses
that SA needs to know about, but in this case it does not. When SA tries to
create a mirror of one of these threads, it fails with:
std
16 matches
Mail list logo
