harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Natalya Golovleva (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-1417) [DRLVM] Fixed bugs in lazy exception optimization pass
Date Mon, 25 Sep 2006 14:28:51 GMT
    [ http://issues.apache.org/jira/browse/HARMONY-1417?page=comments#action_12437572 ] 
Natalya Golovleva commented on HARMONY-1417:

I cannot reproduce the failure.

The test Test2_LE successfully runs before and after patch applying and shows performance

The checks were done on 
-	SUSE LINUX Enterprise Server 9 (i586), gcc version 3.3.3 (SuSE Linux);
-	Fedora Core release 5 (Bordeaux), gcc version 4.1.0 20060304 (Red Hat 4.1.0-3);
-	Ubuntu 6.06, gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5).
gcc 4.1.0 and gcc 4.0.3 usage requires additional patch applying to avoid compilation errors.

Does it make sense to investigate another versions of gcc?

> [DRLVM] Fixed bugs in lazy exception optimization pass
> ------------------------------------------------------
>                 Key: HARMONY-1417
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1417
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>            Reporter: Natalya Golovleva
>         Assigned To: Geir Magnusson Jr
>            Priority: Minor
>         Attachments: HARMONY-1417.patch, Test2_LE.java, Test2_LE_results.doc, Test2_LE_results.txt,
Test_LE.java, Test_LE.java
>     Fixed bugs in lazy exception optimization pass.
>     Replaced lazyexc optpass after inline optpass in server and server_static emconf
>     Fixed bugs in lazy exception optimization pass:
>     1. Permitted to have more then one chknull instructions for exception initializer
>     2. Added check that call exception initializer instruction is present in the code.
>     3. Changed side effect indication for stvar instruction from true to false.
>     The jira depends on HARMONY-1363.

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


View raw message