Loading... (original) (raw)

Today, GC barriers or BarrierSet are called explicitly around accesses that require specific barriers.
It would be desirable if instead accesses are annotated with declarative semantics. Instead of calling different barriers on BarrierSet in different situations explicitly that makes sense for some GCs and not others, this new approach should declare what property makes the access special and let the API automatically generate the correct barriers.

relates to

Enhancement - null JDK-8202377 Modularize C2 GC barriers

JEP - Java Enhancement Proposal JDK-8163329 JEP 304: Garbage Collector Interface

Bug - A problem which impairs or prevents the functions of the product. JDK-8199220 Zero build broken after 8195103, 8191102 and 8189871

Bug - A problem which impairs or prevents the functions of the product. JDK-8202540 Zero fastdebug build is broken after JDK-8189871 (Refactor GC barriers to use declarative semantics)

Bug - A problem which impairs or prevents the functions of the product. JDK-8186787 clang-4.0 SIGSEGV in Unsafe_PutByte

Enhancement - null JDK-8207800 always_do_update_barrier is unused

Enhancement - null JDK-8250844 Make sure {type,obj}ArrayOopDesc accessors check the bounds

Enhancement - null JDK-8272723 Don't use Access API to access primitive fields

(3 relates to)