As far as I can tell, resolveFrameIndex is supposed to be
called with a legal offset, so inserting an add shouldn't be
necessary.
Details
Details
- Reviewers
• tstellarAMD arsenm
Diff Detail
Diff Detail
Event Timeline
Comment Actions
I'm not deep enough into this code to really say what's expected, but I remember changing something there because the ADD path _was_ triggered (although I'm not sure whether it was here or in materializeFrameBaseRegister or both). The offending shader is attached to the bug report at https://bugs.freedesktop.org/show_bug.cgi?id=96602, perhaps you could check if that compiles with this change?