Fursov and Alex,
Since the JIT/VM can determine if GC needs write barrier by querying
gc_requires_barriers(), could you update your patch so that the flag
for doWB will be set when this function returns TRUE? This has no
impact on other GCs that don't require write barrier.
Thanks,
xiaofeng
On
Yes, we'll do.
On 10/10/06, Xiao-Feng Li [EMAIL PROTECTED] wrote:
Fursov and Alex,
Since the JIT/VM can determine if GC needs write barrier by querying
gc_requires_barriers(), could you update your patch so that the flag
for doWB will be set when this function returns TRUE? This has no
impact
Xiaofeng,
I've just submitted http://issues.apache.org/jira/browse/HARMONY-1806.
It introduces write barriers for Java and also slightly changes the
options processing.
After the HARMONY-1806, the GC's gc_requires_barriers() will be taken
into account.
If gc_requires_barriers()==true, then
Good work and thanks, Alex!
-xiaofeng
On 10/10/06, Alex Astapchuk [EMAIL PROTECTED] wrote:
Xiaofeng,
I've just submitted http://issues.apache.org/jira/browse/HARMONY-1806.
It introduces write barriers for Java and also slightly changes the
options processing.
After the HARMONY-1806, the
Thanks to Fursov and Alex for the write barrier submission. JIRA-1580
will be closed.
Wish is committed as soon as possible that people can run GCv5 with it.
http://issues.apache.org/jira/browse/HARMONY-1785
Thanks,
xiaofeng
On 10/9/06, Mikhail Fursov [EMAIL PROTECTED] wrote:
To keep this
Good news is, I tried the write barrier implementation with today's
SVN head, it runs with GCv5 perfectly.
Well the running of GCv5 exposes some debug problem in DRLVM threading
part. I need add two lines of code in GCv5 to work around the problem.
I will start another thread to describe it.
