Making it easier to work with shaders https://git.yummers.dev/slang.git/atom?h=master 2018-02-16T17:04:44+00:00 2018-02-16T17:04:44+00:00 Tim Foley tfoleyNV@users.noreply.github.com 2018-02-16T17:04:44+00:00 urn:sha1:1b93da040ef00836438437e998c1c9584e3fd4ac * Fix bugs around IR legalization of GLSL input/output - Add case to handle assignment of one `ScalarizedVal::Flavor::address` to another (still need to make sure we are handling all the possible cases there) - Revamp logic for creating global variable declarations for varying inputs/outputs. - Actually handle creating array declarations (not sure if binding locations will be correct) - Properly deal with offsetting of locations for nested fields - Only create varying input/output layout information as needed for the separate `in` and `out` variables we create to represent a single HLSL `inout` varying * During SSA generation, recursively remove trivial phis This is actually written up in the original paper I used as a reference, but I hadn't implemented the case yet. When you eliminate one phi as trivial (because its only operands were itself and at most one other value), you might find that another phi becomes trivial (because it had this phi as an operand, but now it will have the other value...). The one thing that made any of this tricky is that our "phi" nodes are really block parameters, and thus they don't technically have operands (`IRUse`s). The `IRUse`s for each phi were being tracked in a separate array, and had their `user` field set to null. With this change, I set their `user` to be the corresponding `IRParam` for the phi (and that means I changed `IRParam` to inherit from `IRUser` even though it shouldn't really be required). * Re-build SSA form after specialization/legalization The main reason to do this is that legalization might scalarize types, and thus might allow us to clean up resource-type local variables that we were not able to clean up when they were part of an aggregate. Note: we shouldn't really need to do this, because the front-end should actually be guaranteeing that types that include resources are used in "safe" ways, but we currently don't have the analyses required to support that. * Give an error message if we get GLSL input The API and command-line interface still recognize and nominally support GLSL input files, because they need to be supported in the "pass-through" mode. This change just adds an error message if we encounter a GLSL input file in anything other than "pass-through" mode. 2017-07-12T17:18:11+00:00 Tim Foley tfoley@nvidia.com 2017-07-12T17:18:11+00:00 urn:sha1:2c6c501b36db9e7991c3f7999451b70f12329ecc - This also adds reflection API for querying: - Entry point name - Entry point parameter list 2017-07-11T19:18:13+00:00 Tim Foley tfoley@nvidia.com 2017-07-11T19:18:13+00:00 urn:sha1:0cd5602383d1ae85276eacec69d51a15a9e975f4 - Update stdlib so taht `image*` types have read-write access encoded in their type - TODO: this isn't 100% right, since there are GLSL qualifiers that might override this - Add a test case to verify that the reflection API reports `image*` parameters