Skip to content
Snippets Groups Projects
  1. Jan 28, 2019
  2. Jan 24, 2019
    • erwan's avatar
      Automate version numbering using Semantic Versionning (semantic-release-gitlab) · 9beabcb2
      erwan authored
      https://www.npmjs.com/package/semantic-release-gitlab
      
      from https://semver.org/ :
        Given a version number MAJOR.MINOR.PATCH, increment the:
      
        - MAJOR version when you make incompatible API changes,
        - MINOR version when you add functionality in a backwards-compatible manner, and
        - PATCH version when you make backwards-compatible bug fixes.
      
      For MAJOR, choosing 6 is obvious.
      
      From Minor it's not clear. This number is supposed to reflect the number of
      add functuionnality, so starting at 0 is not great.
      
      The current version is 1.762, but starting at 762 would be wrong too,
      as most do not deals with new functionnalyties.
      
      In a ideal word, I should use the log and tag every commit tha deals with a new
      functionnalyty, but there is a lot of commits (762).
      
      Hence I,'ve decided to choose 100.
      6.100.1
      9beabcb2
  3. Dec 03, 2018
    • Erwan Jahier's avatar
      Remove a clutch that causes bad error messages and seems useless. · 67eb59fc
      Erwan Jahier authored
      It causes bad error messages in the case were the parametric node is undefined.
      
      e.g., the equation
      
        S=if(M[n-1]) then (entiernat<<n>>(M)-puiss<<n+1>>(2)) else entiernat<<n>>(M);
      
      raises "Error: Bad number of (static) arguments: 0 expected, and 1 provided."
      when entiernat is undefined
      
      It seems useless because no test is broken. The comment mention node
      parameters that themselves have parameters. But it is the case for
      test/should_work/Gyroscope2.lus, and it is still working.
      67eb59fc
  4. Oct 09, 2018
  5. Jul 10, 2018
  6. Jul 06, 2018
  7. Jul 04, 2018
  8. Jul 02, 2018
  9. Apr 27, 2018
  10. Mar 28, 2018
  11. Mar 23, 2018
  12. Mar 21, 2018
  13. Feb 22, 2018
  14. Jan 12, 2018
  15. Dec 18, 2017
  16. Dec 14, 2017
  17. Dec 08, 2017
  18. Dec 01, 2017
  19. Nov 30, 2017
  20. Oct 04, 2017
  21. Sep 27, 2017
  22. Sep 12, 2017
  23. Sep 08, 2017
  24. Sep 06, 2017
  25. Aug 22, 2017
  26. Aug 18, 2017
    • erwan's avatar
      -lv4: expand nodes because array expansion require nodes to be expanded. · 1057e2e1
      erwan authored
      nb: the 2 tests that now pass pass for other reasons (because of a change in
      rdbg 1.108)
      1057e2e1
    • erwan's avatar
      --gen-autotest: assertions were copied in the Lutin file without parenthesis · 39005635
      erwan authored
      I've done the same fix in LicDump actually to be sure (more parenthesis can't hurt).
      
      fix carligths.lus which was badly initialized
      39005635
    • erwan's avatar
      Do dep-loop checking before removing alias, otherwise some variables disappear ! · b13c9efb
      erwan authored
      And it is now done only by Lic2soc (L2lCheckLoops is not used anymore)
      
      Also, during this change, I was bitten again by the « "__" versus "::" in ident
      names » problem again.
      
      The core of this problem is due to the fact that I use LicDump both for
      (1) dealing with internal ident names
      (2) generating lustre files
      
      Because of (2), ident names may depend on the ec or the v4 option. hence, internal
      names were sometimes translated with "__" instead of "::".
      
      To (try to) fix that, I've added a boolean flag to all "to_string" functions that
      states whether the function is used for internal purposes, or for generating lustre
      files.
      
      It was quite a boring change, that triggered other problems, that I've fixed
      in this (too long) commit :
       - -esa should force -en, otherwise bad things happen (-esa is used for -ec anyway)
       - in -esa mode, #/nor inputs tuples of bool, not arrays
       - fix the list of predi op that returns a type different that its arg (SocPredef)
      b13c9efb
  27. Jul 18, 2017
  28. Jul 12, 2017
  29. Jul 10, 2017
  30. Jul 05, 2017
    • erwan's avatar
      -eeb: Extern nodes interface variables were not expanded. · 14a42a03
      erwan authored
      Also, -eeb is now the default when using -ec.
      14a42a03
    • erwan's avatar
      More work on the -eeb option. · 6f975e9b
      erwan authored
      It was generetaing wrong code in conjunction with -ec.
      
      In particular, it was generating n-any "and" instead of binary "and".
      
      Also, I needed (in L2LExpandEnum) to generated a Lic.ARRAY of const
      instead of a Lic.Array_const_eff so that LicDump properly generated
      ec code.
      6f975e9b
  31. Jul 04, 2017
    • erwan's avatar
      More work on the -eeb option. · a6fab49a
      erwan authored
      To do that, I have created a new dedicated module L2lExpandEnum, that
      actually also deals with -eei (which was probably wrong, even if I
      have not counter-exemple).
      
      Use 1-hot encoding instead of log-encoding
      
      I've fixed a bug in L2lExpandArrays that occurs on equation such as
        some_bool = (some_array1 = some_array2);
      
      Also, I've rewritten Lv6Compile for more readability
      
      Remove duplicated code when using SocMap.find and co
      a6fab49a
Loading