http://bugs.freedesktop.org/show_bug.cgi?id=23946
--- Comment #13 from Ian Romanick 2009-09-16 15:44:14
PST ---
(In reply to comment #11)
> (In reply to comment #8)
> > I did check the r200 and registers support 8bits for offset but vertex
> > program
> > compiler doesn't support negative
http://bugs.freedesktop.org/show_bug.cgi?id=23946
--- Comment #12 from Alex Deucher 2009-09-16 11:42:04 PST ---
(In reply to comment #11)
>
> I'm pretty sure when I wrote that code in the r200 driver it didn't work with
> fglrx. I think I quickly tried negative offsets but couldn't get it t
http://bugs.freedesktop.org/show_bug.cgi?id=23946
--- Comment #11 from Roland Scheidegger
2009-09-16 10:34:49 PST ---
(In reply to comment #8)
> (In reply to comment #6)
> > (In reply to comment #4)
> > > Do most other GL drivers allow a larger range of offsets? We could easily
> > > raise
http://bugs.freedesktop.org/show_bug.cgi?id=23946
--- Comment #10 from Sven Arvidsson 2009-09-16 09:01:58 PST ---
*** Bug 23960 has been marked as a duplicate of this bug. ***
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail bec
http://bugs.freedesktop.org/show_bug.cgi?id=23946
Ian Romanick changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
http://bugs.freedesktop.org/show_bug.cgi?id=23946
--- Comment #8 from Pauli 2009-09-16 07:55:10 PST ---
(In reply to comment #6)
> (In reply to comment #4)
> > Do most other GL drivers allow a larger range of offsets? We could easily
> > raise them in Mesa.
>
> It looks like all the hardwa
http://bugs.freedesktop.org/show_bug.cgi?id=23946
--- Comment #7 from Brian Paul 2009-09-16 07:49:43
PST ---
Perhaps we should add a ctx->Const.Vertex/FragmentProgram.MaxAddrOffset field
rather than hard-code a value in the parser.
The range would be [-MaxAddrOffset-1 , MaxAddrOffset].
-
http://bugs.freedesktop.org/show_bug.cgi?id=23946
--- Comment #6 from Ian Romanick 2009-09-16 07:38:23
PST ---
(In reply to comment #4)
> Do most other GL drivers allow a larger range of offsets? We could easily
> raise them in Mesa.
It looks like all the hardware we support should handle
http://bugs.freedesktop.org/show_bug.cgi?id=23946
--- Comment #5 from Henri Verbeet 2009-09-15 08:52:23 PST
---
(In reply to comment #4)
> Do most other GL drivers allow a larger range of offsets? We could easily
> raise them in Mesa.
>
Nvidia and fglrx do, I'm not completely sure about A
http://bugs.freedesktop.org/show_bug.cgi?id=23946
--- Comment #4 from Brian Paul 2009-09-15 07:53:31
PST ---
Do most other GL drivers allow a larger range of offsets? We could easily
raise them in Mesa.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- Yo
http://bugs.freedesktop.org/show_bug.cgi?id=23946
--- Comment #3 from Henri Verbeet 2009-09-15 00:25:29 PST
---
(In reply to comment #2)
> There's another issue but it's a problem with Wine.
>
> The following vertex program is illegal:
>
> !!ARBvp1.0
> PARAM C[66] = { program.env[0..65] }
http://bugs.freedesktop.org/show_bug.cgi?id=23946
--- Comment #2 from Brian Paul 2009-09-14 16:43:44
PST ---
There's another issue but it's a problem with Wine.
The following vertex program is illegal:
!!ARBvp1.0
PARAM C[66] = { program.env[0..65] };
ADDRESS A0;PARAM zero = {0.0, 0.0, 0.0
http://bugs.freedesktop.org/show_bug.cgi?id=23946
--- Comment #1 from Brian Paul 2009-09-14 16:30:27
PST ---
OK, I think I found the issue here.
Mesa links multiple shaders by concatenating them together then recompiling.
When the shaders contain #version directives the extra/redundant #ve
13 matches
Mail list logo