1. 28 Jun, 2019 7 commits
  2. 14 Mar, 2019 1 commit
  3. 04 Mar, 2019 1 commit
  4. 15 Feb, 2019 1 commit
    • Andres Gomez's avatar
      mesa: INVALID_VALUE for wrong type or format in Clear*Buffer*Data · a43596df
      Andres Gomez authored
      Instead of generating a GL_INVALID_ENUM error when the type or format
      is incorrect while using glClear{Named}Buffer{Sub}Data, generate
      GL_INVALID_VALUE.
      
      From page 72 (page 94 of the PDF) of the OpenGL 4.6 spec:
      
        " An INVALID_VALUE error is generated if type is not one of the
          types in table 8.2.
      
          An INVALID_VALUE error is generated if format is not one of the
          formats in table 8.3."
      
      Fixes the following test:
      KHR-GL45.direct_state_access.buffers_errors
      
      v2: correct the doxygen documentation.
      
      Cc: Pi Tabred <servuswiegehtz@yahoo.de>
      Cc: Brian Paul <brianp@vmware.com>
      Signed-off-by: Andres Gomez's avatarAndres Gomez <agomez@igalia.com>
      Reviewed-by: Tapani Pälli's avatarTapani Pälli <tapani.palli@intel.com>
      a43596df
  5. 20 Sep, 2018 1 commit
    • Brian Paul's avatar
      mesa: use GLsizeiptrARB, GLintptrARB in bufferobj.c · 35ea66a6
      Brian Paul authored
      The function pointer declarations in dd.h for the BufferData() and
      BufferSubData() use the ARB-suffixed datatypes.  This patch changes
      the buffer_data_fallback() and buffer_sub_data_fallback() functions
      to use those datatypes too.
      
      This fixes a build warning when building 32-bit libraries.  Evidently,
      GLsizeiptrARB and GLsizeiptr are defined differently in that situation.
      
      All all implementations of these driver hooks use the ARB-suffixed
      types.
      Reviewed-by: Mathias Fröhlich's avatarMathias Fröhlich <Mathias.Froehlich@web.de>
      35ea66a6
  6. 29 Jun, 2018 1 commit
  7. 17 May, 2018 1 commit
  8. 23 Feb, 2018 1 commit
  9. 06 Feb, 2018 1 commit
    • Mathias Fröhlich's avatar
      mesa: Use atomics for buffer objects reference counts. · 2313c33e
      Mathias Fröhlich authored
      The mutex is currently used for reference counting and updating
      the minmax index cache.
      The change uses atomics directly for reference counting and
      the mutex for the minmax cache.
      This is safe since the reference count is not modified beside
      in _mesa_reference_buffer_object where atomics aim to be used.
      While using the minmax cache, the calling code holds a reference
      to the buffer object. Thus unreferencing or even referencing the
      buffer object does not need to be serialized with accessing
      the minmax cache.
      The change reduces the time _mesa_reference_buffer_object_ takes
      by about a factor of two when looking at perf results for some
      of my favorite use cases.
      Signed-off-by: Mathias Fröhlich's avatarMathias Fröhlich <Mathias.Froehlich@web.de>
      Reviewed-by: Brian Paul's avatarBrian Paul <brianp@vmware.com>
      2313c33e
  10. 09 Nov, 2017 1 commit
  11. 23 Oct, 2017 1 commit
  12. 10 Oct, 2017 4 commits
  13. 03 Oct, 2017 1 commit
  14. 24 Aug, 2017 1 commit
  15. 22 Aug, 2017 1 commit
  16. 08 Aug, 2017 1 commit
  17. 06 Aug, 2017 2 commits
  18. 02 Aug, 2017 4 commits
  19. 31 Jul, 2017 2 commits
  20. 27 Jul, 2017 1 commit
  21. 26 Jul, 2017 4 commits
  22. 28 Jun, 2017 2 commits