RFR: 8027545: Improve object array chunking test in G1's copy_to_survivor_space

Kim Barrett kbarrett at openjdk.java.net
Fri Sep 11 04:52:11 UTC 2020


On Thu, 10 Sep 2020 21:42:01 GMT, Stefan Johansson <sjohanss at openjdk.org> wrote:

>> See response above about the name of _partial_objarray_chunk_size.  But I should probably be consistent about objarray
>> vs objArray.  Since objArray is what it is over in runtime oop-land I'm going to go with that.
>
> Again, we have different taste. We very seldom go with camel-case in members and especially in the middle it looks
> strange. Looking through the GC-code I find mostly `objarray` or `obj_array`

You are right; in gc code, it seems "objarray" is used almost exclusively.  The one exception I found seems to be
around the G1CMObjArrayProcessor, where some camel-case has snuck in, such as G1ConcurrentMark::_objArray_processor. So
I'll use "objarray".

-------------

PR: https://git.openjdk.java.net/jdk/pull/90



More information about the hotspot-gc-dev mailing list