You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Ivashin Sergey (JIRA)" <ji...@apache.org> on 2006/10/31 15:11:29 UTC

[jira] Updated: (HARMONY-2016) Jitrino PMF Logger bugs

     [ http://issues.apache.org/jira/browse/HARMONY-2016?page=all ]

Ivashin Sergey updated HARMONY-2016:
------------------------------------

    Attachment: H-2016.patch

The patch fixes 3 PMF Logger bugs.
To fix the last bug, new form of CompilationContext constructor is introduced to copy some data from existing CompilationContext. This form used in inliner and escanalyzer to start new compilation.

> Jitrino PMF Logger bugs
> -----------------------
>
>                 Key: HARMONY-2016
>                 URL: http://issues.apache.org/jira/browse/HARMONY-2016
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: all platforms
>            Reporter: Ivashin Sergey
>         Attachments: H-2016.patch
>
>
> There are 3 known related PMF Logger bugs:
> (1) concurrent write from different Jits
> When info stream is enabled (-Djit.arg.log=info) in server mode of Jitrino, resulting file (log/info.log) is full of garbage, because of concurrent write to the file from SD1_OPT,SD2_OPT and JET_CLINIT Jits.
> (2) enabling  stream for multiple instances of the same action
> For example, -Djit.arg.log.bp_regalloc=ct should enable ct stream for both instances of bp_regalloc, but it does not.
> (3)  write with new CompilationContext in escanalyzer.cpp
> Log stream is not enabled for new compilation that starts by escanalyzer.cpp.

-- 
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