skia2/tests/sksl/errors/Ossfuzz40479.glsl

### Compilation failed:

error: 1: integer is out of range for type 'int': 4016112253
error: 1: array size must be an integer
error: 1: type 'void' may not be used in an array
error: 10: expected ']', but found ''
error: 10: expected an identifier, but found ''
5 errors
Detect and properly handle swizzles of out-of-range literal values. Change-Id: Ic30c48dce0cb0072f07defcdb0b9e60b94f50818 Bug: oss-fuzz:40479 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/465392 Commit-Queue: John Stiles <johnstiles@google.com> Commit-Queue: Brian Osman <brianosman@google.com> Auto-Submit: John Stiles <johnstiles@google.com> Reviewed-by: Brian Osman <brianosman@google.com> 2021-10-29 18:28:32 +00:00			`### Compilation failed:`

			`error: 1: integer is out of range for type 'int': 4016112253`
Fix error with inlined literals overflowing their types. It's possible to write code containing errors that are only apparent once the inliner runs. For instance, a function which takes a short and returns its negative it is valid for most inputs, but undefined for -32768 (because +32768 does not fit in a short). A function which takes floats and casts them to ints is valid for many inputs, but not valid if you pass in 5 billion. This CL restructures our out-of-range integer error detection to report errors cleanly in these cases instead of asserting. It also refactors the range checking code to be usable in situations where we don't yet have a Literal expression. Change-Id: I98f0be63bf9afbbf1ab90233fa86d380cfae42b4 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/466439 Commit-Queue: John Stiles <johnstiles@google.com> Auto-Submit: John Stiles <johnstiles@google.com> Reviewed-by: Brian Osman <brianosman@google.com> 2021-11-02 13:49:02 +00:00			`error: 1: array size must be an integer`
Detect and properly handle swizzles of out-of-range literal values. Change-Id: Ic30c48dce0cb0072f07defcdb0b9e60b94f50818 Bug: oss-fuzz:40479 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/465392 Commit-Queue: John Stiles <johnstiles@google.com> Commit-Queue: Brian Osman <brianosman@google.com> Auto-Submit: John Stiles <johnstiles@google.com> Reviewed-by: Brian Osman <brianosman@google.com> 2021-10-29 18:28:32 +00:00			`error: 1: type 'void' may not be used in an array`
Add expected errors to every test file. This was (crudely) automated with shell scripts: http://go/paste/5484300603490304 Change-Id: Ic9e1c93112772d303d1158eb26d995f27b439eba Bug: skia:12665 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/505637 Reviewed-by: Brian Osman <brianosman@google.com> Commit-Queue: John Stiles <johnstiles@google.com> Auto-Submit: John Stiles <johnstiles@google.com> 2022-02-08 17:19:26 +00:00			`error: 10: expected ']', but found ''`
			`error: 10: expected an identifier, but found ''`
Fix error with inlined literals overflowing their types. It's possible to write code containing errors that are only apparent once the inliner runs. For instance, a function which takes a short and returns its negative it is valid for most inputs, but undefined for -32768 (because +32768 does not fit in a short). A function which takes floats and casts them to ints is valid for many inputs, but not valid if you pass in 5 billion. This CL restructures our out-of-range integer error detection to report errors cleanly in these cases instead of asserting. It also refactors the range checking code to be usable in situations where we don't yet have a Literal expression. Change-Id: I98f0be63bf9afbbf1ab90233fa86d380cfae42b4 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/466439 Commit-Queue: John Stiles <johnstiles@google.com> Auto-Submit: John Stiles <johnstiles@google.com> Reviewed-by: Brian Osman <brianosman@google.com> 2021-11-02 13:49:02 +00:00			`5 errors`