Ignore:
Timestamp:
Nov 15, 2011, 5:11:19 PM (9 years ago)
Author:
tranquil
Message:
  • added an option to not use ternary expressions in costs, to accomodate frama-c explosion of such expressions
  • corrected some typos in comments
  • added a check for well behaved for loops in loop unrolling, but intelligent unrolling is not done yet
  • TODO: peeling and unrolling can contradict preciseness (with difference between introduced branches around 2 cycles). I guess it can be corrected easily
File:
1 edited

Legend:

Unmodified
Added
Removed
  • Deliverables/D2.2/8051-indexed-labels-branch/src/languages.mli

    r1433 r1507  
    7171val labelize : ast -> ast
    7272
    73 (** [annotate input_ast target_ast] inserts cost annotations into the input AST
    74     from the (final) target AST. It also returns the name of the cost variable
    75     and the name of the cost increment function. *)
    76 val annotate : ast -> ast -> (ast * string * string)
     73(** [annotate cost_tern input_ast target_ast] inserts cost annotations into the
     74    input AST from the (final) target AST. It also returns the name of the cost
     75    variable and the name of the cost increment function. The [cost_tern] flag
     76    rules whether cost increments are given by ternary expressions or branch
     77    statements. *)
     78val annotate : bool -> ast -> ast -> (ast * string * string)
    7779
    7880(** [interpret debug ast] runs the program [ast] from the default initial
Note: See TracChangeset for help on using the changeset viewer.