1. 03 Jan, 2017 1 commit
  2. 15 Mar, 2016 1 commit
  3. 09 Sep, 2015 1 commit
  4. 27 Aug, 2015 2 commits
  5. 26 Aug, 2015 1 commit
  6. 16 Jul, 2015 1 commit
  7. 21 Apr, 2015 1 commit
  8. 18 Apr, 2015 1 commit
  9. 20 Mar, 2015 1 commit
  10. 19 Mar, 2015 1 commit
  11. 20 Sep, 2014 1 commit
  12. 10 Sep, 2014 1 commit
  13. 02 Sep, 2014 2 commits
  14. 24 Jul, 2014 1 commit
  15. 10 Jun, 2014 1 commit
  16. 27 May, 2014 2 commits
  17. 14 Mar, 2014 3 commits
  18. 22 Jan, 2014 1 commit
  19. 14 Dec, 2013 1 commit
  20. 12 Dec, 2013 1 commit
  21. 03 Dec, 2013 2 commits
  22. 12 Nov, 2013 1 commit
  23. 08 Nov, 2013 1 commit
  24. 03 Nov, 2013 1 commit
    • Andrei Paskevich's avatar
      allow printers to produce "urgent output" · c0e146fa
      Andrei Paskevich authored
      this is useful to declare on-the-fly a new sort which replaces
      a complex type. Otherwise, the printer has to traverse any term
      twice: first, to detect complex types, second, to print the term.
      c0e146fa
  25. 02 Nov, 2013 1 commit
    • Andrei Paskevich's avatar
      implement printers as memoizing transformations · 9640fb2b
      Andrei Paskevich authored
      also, avoid the "encoding_sort" transformation, if it can be done
      directly in the printer.
      
      On the same example as in the previous commits, this gives 5x
      acceleration together with some memory usage reduction.
      9640fb2b
  26. 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.
      7abeba05
  27. 16 Oct, 2013 1 commit
  28. 11 Oct, 2013 1 commit
  29. 10 Oct, 2013 1 commit
  30. 28 Sep, 2013 1 commit
  31. 13 Mar, 2013 1 commit
  32. 06 Mar, 2013 2 commits
  33. 02 Feb, 2013 1 commit