MSL: Add support for tessellation evaluation shaders.
These are mapped to Metal's post-tessellation vertex functions. The
semantic difference is much less here, so this change should be simpler
than the previous one. There are still some hairy parts, though.
In MSL, the array of control point data is represented by a special
type, `patch_control_point<T>`, where `T` is a valid stage-input type.
This object must be embedded inside the patch-level stage input. For
this reason, I've added a new type to the type system to represent this.
On Mac, the number of input control points to the function must be
specified in the `patch()` attribute. This is optional on iOS.
SPIRV-Cross takes this from the `OutputVertices` execution mode; the
intent is that if it's not set in the shader itself, MoltenVK will set
it from the tessellation control shader. If you're translating these
offline, you'll have to update the control point count manually, since
this number must match the number that is passed to the
`drawPatches:...` family of methods.
Fixes #120.
2019-02-06 00:13:26 +00:00
|
|
|
#pragma clang diagnostic ignored "-Wmissing-prototypes"
|
|
|
|
|
|
|
|
|
|
#include <metal_stdlib>
|
|
|
|
|
#include <simd/simd.h>
|
|
|
|
|
|
|
|
|
|
using namespace metal;
|
|
|
|
|
|
|
|
|
|
struct main0_out
|
|
|
|
|
{
|
|
|
|
|
float4 gl_Position [[position]];
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct main0_in
|
|
|
|
|
{
|
|
|
|
|
float4 Floats [[attribute(0)]];
|
|
|
|
|
float4 Floats2 [[attribute(2)]];
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct main0_patchIn
|
|
|
|
|
{
|
|
|
|
|
patch_control_point<main0_in> gl_in;
|
|
|
|
|
};
|
|
|
|
|
|
2019-08-29 21:39:06 +00:00
|
|
|
inline void set_position(thread float4& gl_Position, thread patch_control_point<main0_in>& gl_in, thread float2& gl_TessCoord)
|
MSL: Add support for tessellation evaluation shaders.
These are mapped to Metal's post-tessellation vertex functions. The
semantic difference is much less here, so this change should be simpler
than the previous one. There are still some hairy parts, though.
In MSL, the array of control point data is represented by a special
type, `patch_control_point<T>`, where `T` is a valid stage-input type.
This object must be embedded inside the patch-level stage input. For
this reason, I've added a new type to the type system to represent this.
On Mac, the number of input control points to the function must be
specified in the `patch()` attribute. This is optional on iOS.
SPIRV-Cross takes this from the `OutputVertices` execution mode; the
intent is that if it's not set in the shader itself, MoltenVK will set
it from the tessellation control shader. If you're translating these
offline, you'll have to update the control point count manually, since
this number must match the number that is passed to the
`drawPatches:...` family of methods.
Fixes #120.
2019-02-06 00:13:26 +00:00
|
|
|
{
|
|
|
|
|
gl_Position = (gl_in[0].Floats * gl_TessCoord.x) + (gl_in[1].Floats2 * gl_TessCoord.y);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
[[ patch(quad, 0) ]] vertex main0_out main0(main0_patchIn patchIn [[stage_in]], float2 gl_TessCoord [[position_in_patch]])
|
|
|
|
|
{
|
|
|
|
|
main0_out out = {};
|
|
|
|
|
set_position(out.gl_Position, patchIn.gl_in, gl_TessCoord);
|
|
|
|
|
return out;
|
|
|
|
|
}
|
|
|
|
|
|
