[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] ARB_robustness and array bounds checking
- To: "Gregg Tavares (wrk)" <email@example.com>
- Subject: Re: [Public WebGL] ARB_robustness and array bounds checking
- From: Kenneth Russell <firstname.lastname@example.org>
- Date: Fri, 21 Oct 2011 11:10:31 -0700
- Cc: Chris Marrin <email@example.com>, "firstname.lastname@example.org webgl" <email@example.com>
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1319220633; bh=DVZAU6L5FjBY6iXh5KpyWoKokBU=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=BprBGoYT8L3uWxyI5UZ5634rz3eqjwRTe7P8EdLW0xFWFuHQ54P1Ov/wFQc9RIiDG /2I4sVCtwtKSPnShgY4pQ==
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-system-of-record; bh=8HKt0F1XHU5FFnrx+i1lO1BoHCtnK7OrLh6nTUryADQ=; b=hXhhQCtFgmxhjfvzgWipiOt+WlhvVeuNvpJgDnjFZImLWtmJDWKBPI+JKTesKQpvuL Cq8z+bJ0XormBLX2aVww==
- Domainkey-signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:date: message-id:subject:from:to:cc:content-type:x-system-of-record; b=Z+vTLsqy+IOSTHSiCvzBrC0qBClT0z7uASGDGBokzdJ67lTiSwlMtRJApKk88hRMF /BVOu4KowbLMO+kJfUQ1A==
- In-reply-to: <CAKZ+BNoMUP3qNRhcCBt1Xc9hxTXvAhLuU1G8=xD0eMCCOtNuzg@mail.gmail.com>
- List-id: Public WebGL Mailing List <public_webgl.khronos.org>
- References: <3AF7E570-2BE9-4D25-BAA5-2F4EA30CD801@apple.com> <CAKZ+BNoMUP3qNRhcCBt1Xc9hxTXvAhLuU1G8=xD0eMCCOtNuzg@mail.gmail.com>
- Sender: firstname.lastname@example.org
On Fri, Oct 21, 2011 at 10:02 AM, Gregg Tavares (wrk) <email@example.com> wrote:
> On Fri, Oct 21, 2011 at 8:20 AM, Chris Marrin <firstname.lastname@example.org> wrote:
>> Currently the WebKit implementation of WebGL keeps around the current
>> index array so it can be used to do bounds checking on draw calls. This is
>> mandated in section 6.4 of the spec. The ARB_robustness extension requires
>> that out-of-bounds array accesses be forbidden. But by my reading it doesn't
>> require the behavior mandated in the WebGL spec. They simply guarantee that
>> no fetches outside the array will happen. Compliant behavior would be to
>> simply return 0 values for these accesses. So bounds checking on the WebGL
>> side would still be required.
>> If this is the case, I think we should make changes so drivers
>> implementing this extension can avoid the WebGL side bounds checking. I'm
>> not sure it's practical to change the ARB_isolation extension at this point.
>> So I would be in favor of changing section 6.4 of the spec to match the
>> behavior required in the extension.
> If I understand correctly the issue with ARB_isolation is there is no
> guarantee the driver is obeying anything. It doesn't report errors for out
> of bounds access so there is no way to test that it's actually working. For
> WebGL we wanted something testable as far as I remember.
This is my recollection as well. There have been discussions in some
of the working groups about strengthening the guarantees in
ARB_robustness' robust buffer access: for example, either clamping the
access to within the buffer, or returning a specified constant value,
so that the extension's behavior is testable. Otherwise the best test
that can be written is one which accesses wildly out-of-range values
and passes if it doesn't crash, which isn't very good.
You are currently subscribed to email@example.com.
To unsubscribe, send an email to firstname.lastname@example.org with
the following command in the body of your email: