Mercurial > hg > graal-compiler
comparison src/share/vm/memory/gcLocker.hpp @ 4873:0382d2b469b2
7013347: allow crypto functions to be called inline to enhance performance
Reviewed-by: kvn
author | never |
---|---|
date | Wed, 01 Feb 2012 16:57:08 -0800 |
parents | 1a2723f7ad8e |
children | 09d00c18e323 |
comparison
equal
deleted
inserted
replaced
4872:aa3d708d67c4 | 4873:0382d2b469b2 |
---|---|
162 // falls into the slow path, or is resumed from the safepoints in | 162 // falls into the slow path, or is resumed from the safepoints in |
163 // the method, which only exist in the slow path. So when _needs_gc | 163 // the method, which only exist in the slow path. So when _needs_gc |
164 // is set, the slow path is always taken, till _needs_gc is cleared. | 164 // is set, the slow path is always taken, till _needs_gc is cleared. |
165 static void lock_critical(JavaThread* thread); | 165 static void lock_critical(JavaThread* thread); |
166 static void unlock_critical(JavaThread* thread); | 166 static void unlock_critical(JavaThread* thread); |
167 | |
168 static address needs_gc_address() { return (address) &_needs_gc; } | |
167 }; | 169 }; |
168 | 170 |
169 | 171 |
170 // A No_GC_Verifier object can be placed in methods where one assumes that | 172 // A No_GC_Verifier object can be placed in methods where one assumes that |
171 // no garbage collection will occur. The destructor will verify this property | 173 // no garbage collection will occur. The destructor will verify this property |