tree ee936d774fb9f434dab78af599665fd834bf3b48
parent b5ad5d4e2f44a8b0af11798e4c5681ba31dd1b22
author Mark Satterthwaite <mark.satterthwaite@epicgames.com> 1565734728 -0400
committer Lukas Hermanns <lukas.hermanns@epicgames.com> 1567701584 -0400

Rework the way arrays are handled in Metal to remove the array copies as they are unnecessary from Metal 1.2. There were cases where copies were not being inserted and others appeared unncessary, using the template type should allow the 'metal' compiler to do the best possible optimisation. The changes are broken into three stages. 1. Allow Metal to use the array<T> template to make arrays a value type. 2. Force the use of C style array declaration for some cases which cannot be wrapped with a template. 3. Threadgroup arrays can't have a wrapper type. 4. Tweak the code to use unsafe_array in a few more places so that we can handle passing arrays of resources into the shader and then through shaders into sub-functions. 5. Handle packed matrix types inside arrays within structs. 6. Make sure that builtin arguments still retain their array qualifiers when used in leaf functions. 7. Fix declaration of array-of-array constants for Metal so we can use the array<T> template.