skia2/tests/sksl/errors/LayoutInStruct.glsl

### Compilation failed:

error: 2: layout qualifier 'binding' is not permitted on a struct field
    layout(binding = 1) int x;  // Not allowed
    ^^^^^^^^^^^^^^^^^^^
error: 3: layout qualifier 'set' is not permitted on a struct field
    layout(set = 0) int y;      // Not allowed
    ^^^^^^^^^^^^^^^
2 errors
Prevent 'binding' and 'set' on struct/interface block fields I should have realized the fuzzer would find this assert when I added it. Now the front-end rejects these layout qualifiers on both struct fields and interface block fields. LayoutInInterfaceBlock.sksl is a reformatted version of the fuzzer input. LayoutInStruct is hand-crafted to trigger the same failure on a different code path. Both would previously assert in the SPIRV generator. Now, neither one gets that far. Bug: oss-fuzz:41347 Change-Id: Iff69d8f5482da7b772e9331c4fd2d58e89813c46 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/476396 Reviewed-by: John Stiles <johnstiles@google.com> Commit-Queue: Brian Osman <brianosman@google.com> 2021-11-24 19:12:41 +00:00			`### Compilation failed:`

			`error: 2: layout qualifier 'binding' is not permitted on a struct field`
Added range highlighting to SkSL error reports SkSL errors now identify the specific range of code they are describing, rather than just the line number. Change-Id: Ifabb3148476f9b4cd8e532f23e5b38e1cf33a87e Reviewed-on: https://skia-review.googlesource.com/c/skia/+/528039 Reviewed-by: John Stiles <johnstiles@google.com> Commit-Queue: Ethan Nicholas <ethannicholas@google.com> 2022-04-06 22:24:52 +00:00			`layout(binding = 1) int x; // Not allowed`
			`^^^^^^^^^^^^^^^^^^^`
Prevent 'binding' and 'set' on struct/interface block fields I should have realized the fuzzer would find this assert when I added it. Now the front-end rejects these layout qualifiers on both struct fields and interface block fields. LayoutInInterfaceBlock.sksl is a reformatted version of the fuzzer input. LayoutInStruct is hand-crafted to trigger the same failure on a different code path. Both would previously assert in the SPIRV generator. Now, neither one gets that far. Bug: oss-fuzz:41347 Change-Id: Iff69d8f5482da7b772e9331c4fd2d58e89813c46 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/476396 Reviewed-by: John Stiles <johnstiles@google.com> Commit-Queue: Brian Osman <brianosman@google.com> 2021-11-24 19:12:41 +00:00			`error: 3: layout qualifier 'set' is not permitted on a struct field`
Added range highlighting to SkSL error reports SkSL errors now identify the specific range of code they are describing, rather than just the line number. Change-Id: Ifabb3148476f9b4cd8e532f23e5b38e1cf33a87e Reviewed-on: https://skia-review.googlesource.com/c/skia/+/528039 Reviewed-by: John Stiles <johnstiles@google.com> Commit-Queue: Ethan Nicholas <ethannicholas@google.com> 2022-04-06 22:24:52 +00:00			`layout(set = 0) int y; // Not allowed`
			`^^^^^^^^^^^^^^^`
Prevent 'binding' and 'set' on struct/interface block fields I should have realized the fuzzer would find this assert when I added it. Now the front-end rejects these layout qualifiers on both struct fields and interface block fields. LayoutInInterfaceBlock.sksl is a reformatted version of the fuzzer input. LayoutInStruct is hand-crafted to trigger the same failure on a different code path. Both would previously assert in the SPIRV generator. Now, neither one gets that far. Bug: oss-fuzz:41347 Change-Id: Iff69d8f5482da7b772e9331c4fd2d58e89813c46 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/476396 Reviewed-by: John Stiles <johnstiles@google.com> Commit-Queue: Brian Osman <brianosman@google.com> 2021-11-24 19:12:41 +00:00			`2 errors`