RFR (XXS): 8026293: Schedule part of G1 pre-barrier late
vladimir.kozlov at oracle.com
Tue Oct 15 10:52:03 PDT 2013
A large part of the G1 write barrier is only used during marking, hence
the code it not commonly executed.
To make the active code segments smaller and better fit the cache these
unused segments should be schedule outside of the common path.
Setting the the first branch of the pre-barrier check to be unlikely
will make the compiler treat the barrier code as cold and hence schedule
it outside of the hot path.
Contributed by Staffan Friberg.
Tested JPRT, jtreg, SPECJEnt, SPECJBB.
More information about the hotspot-compiler-dev