mc-imperial/shader-compiler-bugs

Issues

• spirv-cross w/ spirv-opt produces invalid shader after roundtrip

  #84 opened 7 years ago
  1

• spirv-opt segfault when combining options --compact-ids --inline-entry-points-exhaustive

  #83 opened 7 years ago
  1

• WebGL shader causes HTC One M7 device restart

  #82 opened 7 years ago
  0

• Safari render glitch

  #81 opened 7 years ago
  1

• WebGL shader leaks VRAM data

  #80 opened 7 years ago
  1

• Unreachable control flow causes shader not to render

  #79 opened 7 years ago
  2

• Constant foldable expression with assignment from literal of different type crashes Intel Mesa compiler

  #78 opened 7 years ago
  4

• Intel Mesa crashes with assertion error on code with infinite loop

  #77 opened 7 years ago
  1

• Unreachable control flow instructions lead to wrong image produced

  #76 opened 8 years ago
  0

• Adding a single-iteration do-while loop in a GLSL shader leads to a different image

  #75 opened 7 years ago
  2

• swiftshader rejects a valid shader that uses a struct containing a mat2

  #74 opened 7 years ago
  3

• swiftshader rendering does not terminate

  #73 opened 5 years ago
  4

• Reverse loop triggers assertion error when compiled with debug build of swiftshader

  #72 opened 8 years ago
  2

• Segfault when compiling loop with no initializer for loop variable

  #71 opened 8 years ago
  2

• Adding unreachable "return" and "continue" in a GLSL shader leads to different image

  #70 opened 7 years ago
  2

• Adding dead discard leads to black image

  #69 opened 8 years ago
  3

• Shader rendered with darker background and blue patch on addition of unreachable returns

  #68 opened 8 years ago
  2

• WebGL shader running on Intel Mesa causes machine freeze

  #67 opened 8 years ago
  1

• ANGLE gives error about possible divide by zero at the Direct3D level

  #66 opened 8 years ago
  2

• ANGLE gives hard-to-understand error about an invalid subscript

  #65 opened 8 years ago
  1

• ANGLE gives hard-to-understand error about control paths

  #64 opened 8 years ago
  1

• ANGLE gives internal error

  #63 opened 7 years ago
  3

• Adding a single, meaningless if-else to a shader source leads to different image

  #62 opened 7 years ago
  2

• One-iteration for loop with dead break leads to bad, underterministic image

  #61 opened 8 years ago
  1

• Intel compiler front-end does not accept valid code

  #60 opened 8 years ago
  0

• ANGLE generates invalid HLSL code for shader

  #59 opened 7 years ago
  2

• Wrapping code in ternary operator with macro declaration leads to compilation failure

  #58 opened 8 years ago
  5

• Adding valid code leads to compilation fail

  #57 opened 8 years ago
  6

• Wrapping a float in a ternary operator leads to wrong image being produced

  #56 opened 8 years ago
  3

• Multiplication by 1 and addition with 0 leads to different image

  #55 opened 7 years ago
  2

• Multiplication by unit vector and addition with 0 vector leads to blue image

  #54 opened 8 years ago
  2

• Various dead-code injections lead to slight difference in image produced

  #53 opened 8 years ago
  2

• Wrapping a literal integer in a ternary operator with determined runtime control-flow leads to wrong image

  #52 opened 7 years ago
  3

• Adding an unreachable addition operation leads to difference in rendered image

  #51 opened 8 years ago
  1

• Wrapping code in a single-iteration loop changes the rendered image

  #50 opened 7 years ago
  3

• Adding unreachable break and unreachable continue causes different, darker image

  #49 opened 8 years ago
  2

• Unreachable return statements cause some garbage to be rendered

  #48 opened 7 years ago
  4

• Changing literals to ternary operators with OpenGL function calls leads to black image

  #47 opened 8 years ago
  2

• Rendering shader in WebGL causes various system issues

  #46 opened 7 years ago
  2

• GLSL shader causes bluescreen in Windows when rendered via LibGDX

  #45 opened 8 years ago
  0

• Packing data into vectors causes wrong image to be rendered

  #44 opened 8 years ago
  1

• Packing data into vectors and adding a ternary injection causes wrong image to be rendered

  #43 opened 8 years ago
  1

• Recipient shader rendered incorrectly; adding multiplication by one appears to fix this

  #42 opened 8 years ago
  1

• Adding zero to vector causes black image to be rendered

  #41 opened 8 years ago
  1

• Adding expression after return causes wrong image to be rendered

  #40 opened 8 years ago
  1

• Adding long-running empty loop causes browser to lose WebGL context

  #39 opened 7 years ago
  1

• `vec` literals as statements cause compile errors

  #38 opened 8 years ago
  2

• Adding two unreachable return statements causes garbage to be rendered

  #37 opened 8 years ago
  3

• Adding an empty if statement and other changes causes rendered "worm" to disappear

  #36 opened 7 years ago
  4

• The usual AMD pattern, but with a ternary operator

  #35 opened 8 years ago
  1