Skip to content
Snippets Groups Projects
  1. Jul 07, 2015
  2. Jul 06, 2015
    • Pascal Raymond's avatar
      Probleme des noeud parametrique definis dans un pack : · 03572aa0
      Pascal Raymond authored
      * la syntaxe est changee pour l'accepter
      * la stucture IdSolver (compil "lazy") contient maintenant
        "all_srcs" qui permet d'acceder si besoin a n'importe quelle info source,
        notamment les params statiques des noeuds identifies par "Pack::name"
      03572aa0
  3. Jul 01, 2015
  4. Jun 25, 2015
  5. Jun 24, 2015
  6. Jun 23, 2015
  7. Jun 22, 2015
  8. Jun 19, 2015
  9. Jun 18, 2015
  10. Jun 17, 2015
  11. Jun 12, 2015
  12. Jun 11, 2015
  13. Jun 01, 2015
  14. May 29, 2015
  15. May 22, 2015
  16. Apr 10, 2015
  17. Apr 08, 2015
  18. Apr 07, 2015
  19. Mar 30, 2015
  20. Mar 24, 2015
  21. Mar 20, 2015
  22. Mar 18, 2015
    • Erwan Jahier's avatar
      lic2soc: try a few optimisation wrt Soc.gao scheduling and test opening. · 7d0da0b8
      Erwan Jahier authored
      Indeed, in order to sort Soc.gao, I currently process in 3 stages ;
      1. compute a total ordering of Actions.t according to the deps
      2. transform Actions.t into Soc.gao (List.map)
      3. factorize Soc.gao by looking at consecutive gao that have the same guard
      
      With this change, between steps 1 and 2, I reorder the list of actions
      so that group of independent actions are sorted according to their
      clock. The idea is of course to provide to step 3 more opportunities
      of factorization.
      
      The result is not very convincing yet.
      
      I've also tried to sort the actions wrt their clock before performing
      the toposort. Seems not too bad.
      
      I've kept the old behavior by default though.
      7d0da0b8
  23. Mar 03, 2015
  24. Feb 27, 2015
Loading