Skip to content
Snippets Groups Projects
  1. Mar 22, 2022
  2. Jul 04, 2018
  3. Oct 04, 2017
  4. Jan 14, 2016
  5. Sep 25, 2015
  6. Jun 24, 2015
  7. Jun 18, 2015
  8. Feb 09, 2015
  9. Jan 27, 2015
  10. Jan 22, 2015
  11. Jan 14, 2015
    • Erwan Jahier's avatar
      Fix a bug when using -esa -en -2c on programs with assert · 79e85ff2
      Erwan Jahier authored
      Report by willie (cf mail of 8/10/2014 to get the file)
      
      file:/tmp/modes3x2.lus
      
      lus2lic -esa -en -2c /tmp/modes3x2.lus -n modes3x2
      
      But it gives an error of:
      Error. in file "/mnt/A/wsept/modes3x2_pre_orig_lus2lic_en_esa/modes3x2.lus",
      line 74, col 8 to 8, token '#': only one operator per equation is allowed
      (v04_0, v04_1).
      
      Which is the line:
      assert #(on_off, toggle);
      
      -----------------------------------------------------------------
      
      Actually, refuse programs that uses "#" or "nor" run with -esa and
      -2c|-exec
      
      That means that willie program is now rejected.
      
      Nevertheless, that change migth fix some other programs (that uses
      arrays, and used with -esa and -exec or -2c).
      79e85ff2
  12. Dec 08, 2014
  13. Oct 07, 2014
    • Erwan Jahier's avatar
      lic2soc: factorize some Soc.gao tests · 55efeade
      Erwan Jahier authored
      For the time being, we simple try to factorise out the test of
      consecutive gao that holds on the same clock.
      
      ps : also fix a pb (infinite loop in SortActions.topo_sort)
      introduced in the previous change that, for a strange reason
      (Makefile issue), was not catched by the test (almost all test were
      failing !!).
      
      pps : it actually seems to break quite a lot of test, but its my test
      script that wrong ! since version 527 (we are 534), the compiler used
      to perform the test in the tmp dirs is not upadated ! (well it is,
      but on the wrong machine...).
      
      I commit this change still as it introduces no more test failures.
      55efeade
  14. Oct 02, 2014
  15. Oct 01, 2014
  16. Sep 29, 2014
  17. Sep 09, 2014
  18. Aug 26, 2014
  19. Aug 25, 2014
  20. Aug 22, 2014
  21. Jul 09, 2014
  22. Jul 04, 2014
  23. Jul 01, 2014
    • Erwan Jahier's avatar
      Soc2c: inline ITE soc, to make things simpler. · a4df5e5e
      Erwan Jahier authored
      Indeed, ite are polymorphic, and thus inventing names during soc
      instanciation is error-prone, ugly, innefficient, and increase the
      code size.
      
      Moreover, using C ite to translate them online (ie, without going
      trough a soc) is straigforward
      
      # of unexpected failures	104->101.
      a4df5e5e
  24. Jun 26, 2014
  25. Jun 05, 2014
  26. Dec 11, 2013
    • Erwan Jahier's avatar
      Rewrite the topological sort of actions. · 612d8213
      Erwan Jahier authored
      The main difference is that I use a map instead of list to store
      visited nodes.  The compilation time of normal.ec is divided by 2!!
      (35s->15s)
      
      We do not really see the difference in the time of the non-reg tests
      since the execution of normal.ec still exceeds the 10s timeouts.
      612d8213
  27. Dec 06, 2013
  28. Dec 04, 2013
  29. Nov 28, 2013
  30. Nov 25, 2013
  31. Oct 23, 2013
    • Erwan Jahier's avatar
      A tentative to fix a bug in clock checking appearing in a program of · cc1ab2b7
      Erwan Jahier authored
      Timothy Bourke (trigerred where the clock of some args are some other
      args and when the names of variables are shared between the caller
      and the callee).
      
      The problem is in UnifyClock.f or (in evalClock.ml) ; the current
      change in evalClock.ml fixes the pb in Tim's program, but I suspect
      it is still buggy.
      cc1ab2b7
  32. Jun 03, 2013
  33. May 31, 2013
  34. May 22, 2013
    • Erwan Jahier's avatar
      Fix a bug when expanding nodes (-en). A Node that calls a node that · 499a3f47
      Erwan Jahier authored
      itself calls another node on a non-trivial clock (i.e., using a when)
      was not producing correct code.
      
      I've fixed this by performing the fix-point on nodes rather than on
      equations. Indeed its more natural and efficient, and it avoid the
      problem above. However, I did not really fix the problem, but just
      turn around it. All tests seems to work fine though.
      
      nb : #FAILS=81->80 (and -2 unresolved, but because I fixed the prog)
      499a3f47
Loading