1. 22 Jun, 2015 2 commits
    • Wim Taymans's avatar
      parse: increase array size · 795699b2
      Wim Taymans authored
      Increase the size of the array to hold our variable name and use
      snprintf to avoid overflows.
    • Wim Taymans's avatar
      program: only reuse constants of the same size and value · 4c81fbf1
      Wim Taymans authored
      When reusing an existing constant, make sure not only the value but also
      the size is the same. We then also need to make a name based on the size
      and value so that we can store the same value for different sizes.
      Fixes problem with the bayer functions that used 255 as a 16 and 8 bit
      constant. This was not detected in the unit test because both the backup
      and asm functions do the same error, but it could be seen when a new
      backup function was checked against a older ORC.
  2. 22 May, 2015 4 commits
  3. 10 Apr, 2015 1 commit
  4. 12 Mar, 2015 2 commits
  5. 08 Mar, 2015 1 commit
  6. 27 Feb, 2015 1 commit
    • Edward Hervey's avatar
      testsuite: Put a limit to the memcpy test · d3aed532
      Edward Hervey authored
      Some systems have massive L3 cache that can exceed 64MB, which would
      result in attempting to read/write about our allocated memory.
      If we can deal with 64MB... there's a good chance we can handle above.
  7. 30 Jan, 2015 1 commit
  8. 17 Dec, 2014 2 commits
  9. 10 Dec, 2014 1 commit
  10. 09 Dec, 2014 2 commits
  11. 05 Dec, 2014 1 commit
    • Wim Taymans's avatar
      orcc: allow setting custom backup function · f1cfa5bb
      Wim Taymans authored
      Add a new .backup keyword that instructs the orc compiler to call our
      custom backup function instead of generating one. This is interesting if
      the generated backup function is slower than a plain C implementation.
  12. 03 Dec, 2014 1 commit
  13. 27 Nov, 2014 1 commit
  14. 08 Nov, 2014 1 commit
    • Tim-Philipp Müller's avatar
      orcc: program-c: fix 64-bit parameter loading (loadpq) on big-endian systems · 463295f6
      Tim-Philipp Müller authored
      When passing 64-bit parameters through OrcExecutor, we
      have to split them up into two 32-bit parameters for
      backwards compatibility reasons. When generating C code,
      make sure that we split up 64-bit parameters in the same
      way as loadpq will read them back later. The lower 32 bits
      should end up in params[ORC_VAR_D1+i] and the higher bits
      should end up in params[ORC_VAR_T1+i]. The way it was done
      so far, the higher/lower bits ended up swapped on big endian
      systems, and then got deserialised in swapped order by loadpq.
      This resulted in bogus parameters being used.
      In particular, this broke the gstreamer volume element and
      its unit tests on big endian systems when handling samples
      in F64 format (i.e. doubles).
  15. 26 Sep, 2014 5 commits
  16. 22 Sep, 2014 2 commits
  17. 19 Sep, 2014 7 commits
  18. 18 Sep, 2014 3 commits
  19. 17 Sep, 2014 2 commits