Skip to content
Snippets Groups Projects
  1. Nov 10, 2018
    • ReinUsesLisp's avatar
      gl_shader_decompiler: Guard out of bound geometry shader input reads · 8d4bb10d
      ReinUsesLisp authored
      Geometry shaders follow a pattern that results in out of bound reads.
      This pattern is:
      - VSETP to predicate
      - Use that predicate to conditionally set a register a big number
      - Use the register to access geometry shaders
      At the time of writing this commit I don't know what's the intent of
      this number. Some drivers argue about these out of bound reads. To avoid
      this issue, input reads are guarded limiting reads to the highest
      posible vertex input of the current topology (e.g. points to 1 and
      triangles to 3).
      8d4bb10d
  2. Nov 08, 2018
  3. Nov 07, 2018
  4. Nov 06, 2018
  5. Nov 05, 2018
  6. Nov 04, 2018
  7. Nov 03, 2018
  8. Nov 02, 2018
  9. Nov 01, 2018
Loading