1. 06 Apr, 2018 1 commit
  2. 26 Feb, 2018 2 commits
  3. 04 Feb, 2018 1 commit
  4. 04 Feb, 2017 1 commit
  5. 31 Jan, 2017 1 commit
  6. 01 Oct, 2016 1 commit
  7. 30 Aug, 2016 1 commit
    • Explorer09's avatar
      Mark signal tables 'const' · 1f3d85b6
      Explorer09 authored
      
      
      Specifically, Platform_signals[] and Platform_numberOfSignals. Both are
      not supposed to be mutable. Marking them 'const' puts them into rodata
      sections in binary. And for Platform_numberOfSignals, this aids
      optimization (aids only Link Time Optimization for now). :)
      Signed-off-by: default avatarKang-Che Sung <explorer09@gmail.com>
      1f3d85b6
  8. 30 Apr, 2016 1 commit
  9. 31 Mar, 2016 2 commits
  10. 19 Feb, 2016 1 commit
  11. 18 Feb, 2016 2 commits
  12. 13 Feb, 2016 1 commit
  13. 02 Feb, 2016 1 commit
  14. 15 Jan, 2016 1 commit
    • Explorer09's avatar
      Introduce CLAMP macro. Unify all MIN(MAX(a,b),c) uses. · 6dae8108
      Explorer09 authored
      With the CLAMP macro replacing the combination of MIN and MAX, we will
      have at least two advantages:
      1. It's more obvious semantically.
      2. There are no more mixes of confusing uses like MIN(MAX(a,b),c) and
         MAX(MIN(a,b),c) and MIN(a,MAX(b,c)) appearing everywhere. We unify
         the 'clamping' with a single macro.
      Note that the behavior of this CLAMP macro is different from
      the combination `MAX(low,MIN(x,high))`.
      * This CLAMP macro expands to two comparisons instead of three from
        MAX and MIN combination. In theory, this makes the code slightly
        smaller, in case that (low) or (high) or both are computed at
        runtime, so that compilers cannot optimize them. (The third
        comparison will matter if (low)>(high); see below.)
      * CLAMP has a side effect, that if (low)>(high) it will produce weird
        results. Unlike MIN & MAX which will force either (low) or (high) to
        win. No assertion of ((low)<=(high)) is done in this macro, for now.
      
      This CLAMP macro is implemented like described in glib
      <http://developer.gnome.org/glib/stable/glib-Standard-Macros.html>
      and does not handle weird uses like CLAMP(a++, low++, high--) .
      6dae8108
  15. 13 Jan, 2016 1 commit
  16. 02 Jan, 2016 1 commit
  17. 03 Dec, 2015 1 commit
  18. 16 Nov, 2015 1 commit
  19. 02 Nov, 2015 2 commits
  20. 01 Nov, 2015 1 commit
  21. 25 Oct, 2015 1 commit
  22. 23 Oct, 2015 1 commit
  23. 19 Oct, 2015 1 commit
  24. 06 Oct, 2015 1 commit
  25. 19 Sep, 2015 1 commit
  26. 17 Sep, 2015 1 commit
  27. 14 Sep, 2015 1 commit
  28. 10 Sep, 2015 1 commit
  29. 07 Sep, 2015 1 commit
    • Christian Hesse's avatar
      fix calloc() calls · e8970b6f
      Christian Hesse authored
      * size_t nmemb (number of elements) first, then size_t size
      * do not assume char is size 1 but use sizeof()
      * allocate for char, not pointer to char (found by Michael McConville,
        fixes #261)
      e8970b6f
  30. 20 Aug, 2015 1 commit
  31. 19 Aug, 2015 6 commits