Skip to content
Snippets Groups Projects
  1. Oct 01, 2014
  2. Sep 04, 2014
  3. Aug 27, 2014
  4. Aug 22, 2014
  5. Aug 07, 2014
    • Erwan Jahier's avatar
      non-reg tests: try to remove tests that fail for bad reasons. · 5c16363d
      Erwan Jahier authored
      For instance, do not launch tests that perform result comparison (via
      lurette) on files that contains extern nodes (as they cannot be
      executed) or package.  Package do not work because appending the
      tested lustre file with the generated oracle as I do is wrong in
      presence of package.
      
      Moreover, my current test process is not able to test programs which
      main node IOs are not all on the base clock. I have fixed this by
      patching the examples.
      
      # of expected passes 		1508 -> 1512
      # of unexpected failures	130 -> 84
      5c16363d
  6. Jul 11, 2014
  7. May 21, 2014
  8. May 12, 2014
  9. Feb 20, 2014
  10. Jan 23, 2014
  11. Dec 10, 2013
  12. Dec 06, 2013
  13. May 31, 2013
  14. May 28, 2013
  15. May 06, 2013
  16. Apr 26, 2013
  17. Apr 25, 2013
  18. Apr 24, 2013
  19. Apr 23, 2013
    • Erwan Jahier's avatar
      Fix several issues w.r.t. clocks during node expansion. · cb891dc4
      Erwan Jahier authored
      (1) equations such as
       (x,y,z)=[0,0,0];
      were generated with -en unless -ec was specified.
      
      I've fixed that by always breaking tuples, even when global_opt.ec
      is false (this condition was strange anyway).
      
      (2) During node expansion, I create a fresh variable for each local
      var in the expanded node, but old var names were still appering in
      clock expression
      
      indeed, consider that example :
      var
        c:bool;
        x when c :bool;
      
      I was generating something equivalent to
      
      var
        c_fresh:bool;
        x_fresh when c :bool;
      
      bou... Of course, it was working because in -ec mode, I need to
      remove clock annotation when declaring local variables, which was
      hidding the problem.
      
      nb : because I've change test_lus2lic_no_node to use -lv4 instead of
      -ec to generate the lustre oracle, which exposes new pbs (cf above).
      
      (3) When expanding a node on the base clock with arguments on another
      clock, I was not propagating that information (let's keep the
      finger-crossed and hope the current fix is complete).
      
      nb : the number of failing test cases is the same (5 new pass, but 5
      new fail!!), but it actually is a progression. Indeed, the new test
      failures ares due to the fact that this current change fixes a
      problem that expose yet another one!
      
      Actually, the newly exposed bug is not in the compliler, but in the
      oracle I generate via the --auto-test option ; indeed, for testing
      nodes which not all interface variables are one the base clock, I
      should generate oracle that do take them into account.
      cb891dc4
  20. Apr 22, 2013
  21. Feb 07, 2013
  22. Feb 01, 2013
  23. Oct 26, 2012
  24. Jul 03, 2012
  25. Dec 05, 2011
  26. Dec 05, 2007
  27. Oct 19, 2007
Loading