1. 17 Jan, 2014 2 commits
  2. 28 Nov, 2013 1 commit
  3. 26 Nov, 2013 2 commits
  4. 08 Oct, 2012 1 commit
    • Pfeiffer, Götz's avatar
      Csmbase optimized for speed. · bc76dc39
      Pfeiffer, Götz authored
      
      * The search for a matching interval in a table of break-points was optimized.
        The lookup function now looks first to the previous interval, then the
        intervals below and above the previous one. Only if these intervals don't
        match it performs a binary search across the while break point table.
      * If the functions csm_x, csm_y or csm_z are called with the same values as the
        last time, they do not perform any calculation but return the previous value
        from their internal cache.
      bc76dc39
  5. 21 Nov, 2011 1 commit
  6. 12 Sep, 2011 1 commit
  7. 29 Aug, 2011 1 commit
  8. 26 Aug, 2011 2 commits
  9. 17 Aug, 2011 2 commits
  10. 12 Aug, 2011 1 commit
  11. 18 Apr, 2011 8 commits
  12. 12 Apr, 2011 2 commits
  13. 18 Feb, 2011 1 commit
  14. 23 Oct, 2010 4 commits
  15. 07 Dec, 2009 1 commit
  16. 27 Apr, 2009 2 commits
  17. 09 Jun, 2008 1 commit
  18. 05 Jun, 2008 1 commit
  19. 14 Nov, 2007 2 commits
  20. 06 Jun, 2008 1 commit
  21. 09 Jun, 2008 1 commit
  22. 14 Nov, 2007 1 commit
    • Goetz.Pfeiffer's avatar
      bugfix: csm_x, csm_y, csm_z, csm_dx and csm_dy sometimes returned wrong values · 045a5ab9
      Goetz.Pfeiffer authored
        + bugfix with respect to the on-hold function: The "last" field
          of the csm_Function structure has to exist for each type of
          function that can be applied to the structure, one for
          csm_x(), one for csm_y(), one for csm_z(), for csm_dx() and
          csm_dy(). With only one field, it may happen for example,
          that when "on_hold" is used, csm_x() returns the last returned
          value of csm_y().
        + bugfix with respect to multithreading use:
          the semaphore used in functions like csm_x(), csm_y() and so
          on was given just before a return-statement which did a read-access
          on the function structure. This lead to a race condition where
          it was possible that one call of csm_x() returned the value of
          another call of csm_x() which was called by another task. Together
          with "last" field bug mentioned above, csm_x() could even return
          the value of the last csm_y() call, which is fatal...
      045a5ab9
  23. 22 Nov, 2007 1 commit