Fri, 20 Sep 2013 10:53:28 +0200
8024974: Incorrect use of GC_locker::is_active()
Summary: SymbolTable and StringTable can make calls to GC_locker::is_active() outside a safepoint. This isn't safe because the GC_locker active state (lock count) is only updated at a safepoint and only remains valid as long as _needs_gc is true. However, outside a safepoint_needs_gc can change to false at any time, which makes it impossible to do a correct call to is_active() in that context. In this case these calls can just be removed since the input argument to basic_add() should never be on the heap and so there's no need to check the GC_locker state. This change also adjusts the assert() in is_active() to makes sure all calls to this function are always done under a safepoint.
Reviewed-by: brutisso, dcubed
Contributed-by: per.liden@oracle.com
aoqi@0 | 1 | os_family = linux |
aoqi@0 | 2 | |
aoqi@0 | 3 | arch = ia64 |
aoqi@0 | 4 | |
aoqi@0 | 5 | os_arch = linux_ia64 |
aoqi@0 | 6 | |
aoqi@0 | 7 | lib_arch = ia64 |
aoqi@0 | 8 | |
aoqi@0 | 9 | compiler = gcc |
aoqi@0 | 10 | |
aoqi@0 | 11 | gnu_dis_arch = ia64 |
aoqi@0 | 12 | |
aoqi@0 | 13 | sysdefs = -DLINUX -D_GNU_SOURCE -DIA64 -DCC_INTERP |
aoqi@0 | 14 | |
aoqi@0 | 15 | mark_style = alignment |