1. 09 Nov, 2013 3 commits
  2. 08 Nov, 2013 6 commits
  3. 05 Nov, 2013 2 commits
  4. 04 Nov, 2013 3 commits
  5. 03 Nov, 2013 3 commits
  6. 02 Nov, 2013 2 commits
  7. 01 Nov, 2013 7 commits
    • Andrei Paskevich's avatar
      Term: simplify t_label_copy · 96b8c672
      Andrei Paskevich authored
    • Andrei Paskevich's avatar
      Termcode: do not reallocate buffers · 191d15da
      Andrei Paskevich authored
    • Andrei Paskevich's avatar
      Termcode: do not keep more than actually needed · dfd11796
      Andrei Paskevich authored
      I didn't increment the version just for this fix, so sessions
      are officially broken between the previous commit and this one.
    • Andrei Paskevich's avatar
    • Andrei Paskevich's avatar
      Term: remove redundant *_alpha operations · d93cc40f
      Andrei Paskevich authored
      feel free to revert, if you think we might want to make again the
      distinction between t_equal and t_equal_alpha in future or just
      don't feel like breaking the API.
    • Andrei Paskevich's avatar
      tidying up · 58ff0109
      Andrei Paskevich authored
      also, ensure that t_label_copy does not lose information
    • Andrei Paskevich's avatar
      Trans: do not memoize transformations of goals · 3cdc073f
      Andrei Paskevich authored
      the goal declarations are not shared and thus memoizing transformations
      on them is only interesting if we apply the same transformation on the
      same goal (which may happen when we launch several provers of the same
      family on the same goal). On the other hand, goal declarations are big
      (think WP) and numerous (think goal_split), and keeping them in memory
      is a bad idea.
      The same example from BWare can now be treated with 1/4 of memory:
      why3-replayer : full memoization
      106.81user 7.86system 1:59.32elapsed 96%CPU (0avgtext+0avgdata 1656908maxresident)k
      why3-replayer : no memoization on goals (this commit)
      74.14user 4.24system 1:24.93elapsed 92%CPU (0avgtext+0avgdata 429376maxresident)k
      why3-replayer : no memoization at all
      217.78user 6.25system 3:43.56elapsed 100%CPU (0avgtext+0avgdata 615204maxresident)k
      One side effect of this commit is that polymorphism encoding
      transformations are likely to be memoized only for a short time.
      The transformations that select the type instances to discriminate
      and the types to preserve in encoding are full-task-dependent and
      therefore are not memoized anymore. Thus, as soon the the task that
      contains all the selection metas is GCed, the rest of the chain
      will go, too, and Why3 will have to re-monomorphize the same decls.
      We'll see if this is a problem in practice.
  8. 31 Oct, 2013 1 commit
  9. 30 Oct, 2013 12 commits
  10. 29 Oct, 2013 1 commit
    • Andrei Paskevich's avatar
      Term: do not store t_vars in terms · 7abeba05
      Andrei Paskevich authored
      we still keep bv_vars in the binders, so calculating the set
      of free variables only has to descend to the topmost binders.
      The difference on an example from BWare is quite striking:
      /usr/bin/time why3-replayer : with t_vars
      505.14user 15.58system 8:40.45elapsed 100%CPU (0avgtext+0avgdata 3140336maxresident)k
      /usr/bin/time why3-replayer : without t_vars
      242.96user 12.04system 4:16.31elapsed 99%CPU (0avgtext+0avgdata 2007184maxresident)k
      Not only we take 2/3 of memory, but we also gain in speed (less work
      for the GC, most probably).
      This patch should be tested on big WhyML examples,
      since src/whyml/mlw_*.ml are big users of t_vars.
      Thanks to Guillaume for the suggestion.