To be clear, I'm saying this is broken in Mesa for *any* situation that involves redefining a function that appears in a future GL version or ext. There are some limitations to this, based on when the error is triggered, I don't have the code in front of me. At least it happens for es 3.0.

On Jul 2, 2017 15:10, <bugzilla-daemon@freedesktop.org> wrote:

Comment # 4 on bug 101666 from Ilia Mirkin
The predicate is correct, just never checked. On Jul 2, 2017 15:08, <bugzilla-daemon@freedesktop.org> wrote:
> *Comment # 3 <https://bugs.freedesktop.org/show_bug.cgi?id=101666#c3> on > bug 101666 <https://bugs.freedesktop.org/show_bug.cgi?id=101666> from > Kenneth Graunke <kenneth@whitecape.org> *
> > I don't think you need to change any infrastructure, we just didn't add the > proper built-in availability predicate to the bitfieldExtract functions in > builtin_functions.cpp. it should be trivial to fix - this is by no means a new > case... >
> ------------------------------ > You are receiving this mail because: > > - You are the assignee for the bug.
> > > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev > >


You are receiving this mail because:
  • You are the assignee for the bug.

_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev