harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geir Magnusson Jr (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-1371) [DRLVM][GC] gcv4.1 optimized allocation path
Date Thu, 21 Sep 2006 22:51:24 GMT
    [ http://issues.apache.org/jira/browse/HARMONY-1371?page=comments#action_12436683 ] 
            
Geir Magnusson Jr commented on HARMONY-1371:
--------------------------------------------

This patch breaks DRLVM as of SVN head as of r448725.

C-unit passes, but smoke tests fail, such as gc.Finalizer, gc.Force, gc.PhantomReferenceQueueTest,
gc.PhantomReferenceTest, gc.RefRemove, gc.LIst

Looking at gc.List error output : 

.java: /home/geir/dev/apache/harmony/enhanced/trunk/working_vm/vm/gc/src/selector.cpp:233:
void update_evacuation_area(): Assertion `incr > 0' failed.
SIGABRT in VM code.
Stack trace:
addr2line: '[vdso]': No such file
        1: ?? (܊�ʲ������:-1)
addr2line: '[stack]': No such file
        2: ?? (܊�ʲ������:-1)
        3: raise (??:-1)
        4: ?? (??:-1)
addr2line: '[stack]': No such file
        5: ?? (?:-1)
        6: abort (??:-1)
addr2line: '[stack]': No such file
        7: ?? (bort:-1)
<end of stack trace>


> [DRLVM][GC] gcv4.1 optimized allocation path
> --------------------------------------------
>
>                 Key: HARMONY-1371
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1371
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>         Environment: Linux/Windows
>            Reporter: Ivan Volosyuk
>         Assigned To: weldon washburn
>            Priority: Minor
>         Attachments: gcv41_allocation_optimization_and_more.diff, gcv41_allocation_optimization_and_more.diff
>
>
> Allocation path optimization: reduced cleaned in advance memory.
> Fixed dead finalizible objects detection algorithm.
> Disabled force_gc() algorithm: triggers finalization problem on dacapo benchmark.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message