1. 28 Jun, 2017 1 commit
  2. 27 Jun, 2017 1 commit
  3. 23 Jun, 2017 1 commit
  4. 16 Jun, 2017 1 commit
  5. 12 Jun, 2017 2 commits
  6. 29 May, 2017 1 commit
  7. 24 May, 2017 1 commit
  8. 10 May, 2017 2 commits
  9. 12 Apr, 2017 1 commit
  10. 15 Dec, 2016 1 commit
  11. 23 Nov, 2016 1 commit
    • Sylvain Dailler's avatar
      Add a name_table in proof_node. · e0d6b38d
      Sylvain Dailler authored
      Add a name_table in printer_args.
      Put the definition of name_table in task.ml.
      Build_name_tables only called once in proof_node creation.
      Modified the rest accordingly.
      e0d6b38d
  12. 26 Jul, 2016 1 commit
  13. 19 Jul, 2016 1 commit
    • Johannes Kanig's avatar
      Allow to keep unmatched theories · 4c744eba
      Johannes Kanig authored
      When Why3 is run on a file where some theories have been suppressed, it
      will delete the corresponding theories from the session file.  We now
      add an option keep_unmatched_theories to Session.update_session, which
      keeps all theories. In this commit, this option is always disabled.
      
      This is useful for SPARK, which sometimes only generates part of the
      Why3 file for efficiency reasons, but doesn't want the session file to
      be damaged because of that.
      
      * session.ml
      (import_theory)
      (import_goal)
      (import_proof_attempt)
      (import_transf): new functions to copy a session tree from an old
        session file
      (merge_file): keep old theories when keep_unmatched_theories is true
      * session_scheduler.ml
      (update_session): pass keep_unmatched_theories
      * why3session_lib.ml
      (read_update_session): pass keep_unmatched_theories
      4c744eba
  14. 14 Apr, 2016 1 commit
  15. 15 Mar, 2016 2 commits
  16. 11 Mar, 2016 1 commit
  17. 08 Mar, 2016 1 commit
  18. 17 Nov, 2015 1 commit
    • David Hauzar's avatar
      Query cvc4 for reason of answer unknown and use it for counterexamples. · 5c3038bf
      David Hauzar authored
      When resource limit is hit, cvc4 outputs useless counterexample. Query
      cvc4 for the reason of answer unknown and use the answer to decide
      whether resource limit was hit. If it was hit, do not display the
      counterexample.
      
      * src/driver/call_provers.{ml|mli}
      (parse_prover_run): If the prover answers unknown, get the information
      about the reason of this answer.
      
      * src/printer/smtv2.ml
      (print_prop_decl): Query solver for the reason of answer unknown.
      
      * src/driver/driver.ml
      (load_driver): Initialize Unknown with no information about the reason
      of answer unknown.
      
      * src/session/session.ml
      (load_result): Initialize Unknown with no information about the reason
      of answer unknown.
      
      * src/session/session_scheduler.ml
      (schedule_proof_attempt)
      (edit_proof): Initialize Unknown with no information about the reason
      of answer unknown.
      
      * src/why3session/why3session_lib.ml
      (filter_spec): Initialize Unknown with no information about the reason
      of answer unknown.
      5c3038bf
  19. 10 Nov, 2015 1 commit
  20. 12 Oct, 2015 1 commit
  21. 09 Sep, 2015 3 commits
  22. 11 Jul, 2015 1 commit
  23. 22 Jun, 2015 1 commit
  24. 12 Jun, 2015 1 commit
  25. 10 Jun, 2015 1 commit
  26. 09 Jun, 2015 3 commits
  27. 26 May, 2015 1 commit
  28. 23 May, 2015 1 commit
  29. 23 Mar, 2015 1 commit
  30. 20 Mar, 2015 1 commit
  31. 19 Mar, 2015 1 commit
  32. 19 Sep, 2014 1 commit
  33. 18 Sep, 2014 1 commit