Christian Despres comments

Results 96 comments of


                                            Christian Despres

Allow JITServer AOT cache to work without a shared class cache at the client

Incidentally, that's all the difference seems to be - there are `e5` bytes in a few places in the without-SCC case where there are variously bytes `ad`, `ef`, `ac` in...

Allow JITServer AOT cache to work without a shared class cache at the client

I've found the difference - when `isROMClassShareable()` is true in the rom class creation context, the code path we go down will eventually call `fixReturnBytecodes` on the ROMClass that's been...

Allow JITServer AOT cache to work without a shared class cache at the client

@AlexeyKhrabrov I'd just like to confirm something about deserialization. When the deserializer deals with class chain records from the server currently, it builds up a RAM class chain from the...

Allow JITServer AOT cache to work without a shared class cache at the client

Of course we will still have to check during deserialization that the RAM class chain constructed from the class chain serialization record is compatible with the RAM class chain derived...

Allow JITServer AOT cache to work without a shared class cache at the client

Will a `J9Method *` (corresponding to a `MethodSerializationRecord`) ever be invalidated like a `J9Class *` or `J9ClassLoader *`? At the moment the deserializer only stores the local SCC offset to...

Allow JITServer AOT cache to work without a shared class cache at the client

Here is a high-level explanation of the JITServer AOT cache changes. I gave some background/useful information in the first few sections about how AOT and the JITServer AOT cache currently...