24 Apr
2023
24 Apr
'23
8:27 p.m.
On Mon Apr 24 20:08:52 2023 +0000, Zebediah Figura wrote:
The segfault persists even if the field with the `UNUSED` semantic is removed.
It goes away when `TEXCOORD0` is not duplicated though, for instance
if we make `apple aps[1][1]`: That doesn't make any sense; the duplication doesn't show up in the bytecode at all. There must be something else going on.
Ah, yes, ignore my comment. I got myself really confused here.
Contrary to what I said, it is the `UNUSED` semantic the one that creates the segfault, and when I delete it, the segfault goes away. Yes, there can be a duplicated `TEXCOORD0` input semantic.