On Tue, 2015-12-15 at 14:32 +0200, Tapani Pälli wrote:
> On 12/15/2015 01:25 AM, Timothy Arceri wrote:
> > On Wed, 2015-12-09 at 00:17 +1100, Timothy Arceri wrote:
> > > In core profile even if re-linking fails rendering shouldn't fail
> > > as
> > > the
> > > previous succesfully linked program
On 12/15/2015 01:25 AM, Timothy Arceri wrote:
On Wed, 2015-12-09 at 00:17 +1100, Timothy Arceri wrote:
In core profile even if re-linking fails rendering shouldn't fail as
the
previous succesfully linked program will still be available. It also
shouldn't be possible to have an unlinked program
On Wed, 2015-12-09 at 00:17 +1100, Timothy Arceri wrote:
> In core profile even if re-linking fails rendering shouldn't fail as
> the
> previous succesfully linked program will still be available. It also
> shouldn't be possible to have an unlinked program as part of the
> current rendering state.
In core profile even if re-linking fails rendering shouldn't fail as the
previous succesfully linked program will still be available. It also
shouldn't be possible to have an unlinked program as part of the
current rendering state.
This fixes a subtest in:
ES31-CTS.sepshaderobjs.StateInteraction
