harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Egor Pasko (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-2381) [drlvm][jit] Jitrino help improvements
Date Mon, 04 Dec 2006 12:51:25 GMT
    [ http://issues.apache.org/jira/browse/HARMONY-2381?page=comments#action_12455300 ] 
            
Egor Pasko commented on HARMONY-2381:
-------------------------------------

nice!

Sergey,

are you going to *also* refactor the way each action documents itself? I would prefer if flags
are declared in the same place where their descriptions are defined. Today it is not like
that, you have to edit some showFlags(..) which leads to desynchronization sometimes. Would
be nice to fix it, but, unfortunately, it is a lot of changes.

> [drlvm][jit] Jitrino help improvements
> --------------------------------------
>
>                 Key: HARMONY-2381
>                 URL: http://issues.apache.org/jira/browse/HARMONY-2381
>             Project: Harmony
>          Issue Type: Improvement
>          Components: DRLVM
>            Reporter: Ivashin Sergey
>
> It is proposed to extend Jitrino help with the following commands:
> -Djit.help=<action>
> 	will produce help for the action specified
> -Djit.help=jit
> 	will produce new info on current configuration
> -Djit.help=all
> 	will produce current help + configuration info
> -Djit.help=<anything other>
> 	will produce current help
> Help info on current confuguration will be composed in the following way.
> For each jit available, its name is printed:
> Jit <jit name>
>  
> Further, for each pipeline defined in this jit, its name and filter 
> expression are printed:
>   Pipeline <pipeline name> filter <filter expression>
>  
> For common pipeline, <common> is printed instead of name and no filter 
> clause is printed, because common pipeline has no name and has empty 
> filter. If pipeline has any pipeline-wide arguments (i.e. arguments that
> affect all actions in the pipeline), they are printed directly after
> pipeline name. 
>     arg <arg name>=<arg value>
> In a similar way, all enabled pipeline-wide streams (if any) are printed
>     stream <stream name> file <file name mask>
> Because different streams can have the same name, stream index is 
> printed after the name, so ct[1] and ct[2] are different streams with 
> the same name.
> If jit has non-empty list of enabled actions, it is printed next, one 
> action per line under "Actions" header:
>     Actions
>       <action full name>
> For each action which has specific arguments or streams enabled, 
> they are printed in the form similar to pipeline-wide arguments and 
> streams.
> For Jitrino.Jet, list of actions is not printed, because this jit 
> does not have any actions.

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