Oliver McFadden wrote:
> Hi,
>
> I believe I've found a few bugs caused by the unaliasing of generic vertex
> attributes (commit 095c6699f449ed4803f23e844cc0227743a9c3e1), specifically in
> the file src/mesa/shader/arbprogparse.c:
>
> case VERTEX_ATTRIB_GENERIC:
> {
>
Brian Paul wrote:
> Oliver McFadden wrote:
>> Hi,
>>
>> I believe I've found a few bugs caused by the unaliasing of generic vertex
>> attributes (commit 095c6699f449ed4803f23e844cc0227743a9c3e1), specifically in
>> the file src/mesa/shader/arbprogparse.c:
>>
>> case VERTEX_ATTRIB_GENERIC:
On 1/15/07, Brian Paul <[EMAIL PROTECTED]> wrote:
> Oliver McFadden wrote:
> > I'm also a little confused on how to use generic vertex attributes now. I
> guess
> > it should just be a case of using attributes >= 16 in both the program's
> code,
> > and the vertex program, correct?
>
> Unfortunatel
Should probably do the same thing for ctx->FragmentProgram._Current too.
Can you make that change, Jerome, and test?
-Brian
Keith Whitwell wrote:
> Jerome - this looks good.
>
> Keith
>
> Jerome Glisse wrote:
>> Hi Keith,
>>
>> I have reported few days ago a bug, at least what i thought to be
So, I decided it would be neat to merge all the changes that have
occurred on the Mesa mainline to the vbo branch where I've started
working again.
Naively, I thought something simple like:
git checkout vbo_0_1_branch
git pull
Would do the trick, but that has given me a gazilli
On Mon, 2007-01-15 at 17:35 +, Keith Whitwell wrote:
> So, I decided it would be neat to merge all the changes that have
> occurred on the Mesa mainline to the vbo branch where I've started
> working again.
>
> Naively, I thought something simple like:
>
> git checkout vbo_0_1_branch
Michel Dänzer wrote:
> On Mon, 2007-01-15 at 17:35 +, Keith Whitwell wrote:
>> So, I decided it would be neat to merge all the changes that have
>> occurred on the Mesa mainline to the vbo branch where I've started
>> working again.
>>
>> Naively, I thought something simple like:
>>
>> g
On 1/15/07, Brian Paul <[EMAIL PROTECTED]> wrote:
>
> Should probably do the same thing for ctx->FragmentProgram._Current too.
> Can you make that change, Jerome, and test?
>
> -Brian
>
I commited somethings similar, i haven't really a test case for
fragment program to trigger such bug for fragmen
> Oh yes, and there is some magic to create a branch on the remote, right?
> Am I able to do this myself or to I have to ask a grownup?
Nope.. just push the branch, like
git push origin my-new-branch:my-new-branch
Dave.
--
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airli
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=9625
--- Additional Comments From [EMAIL PROTECTED] 2007-01-15 16:43 ---
Could
On Mon, 2007-01-15 at 20:20 +, Keith Whitwell wrote:
> Michel Dänzer wrote:
> > On Mon, 2007-01-15 at 17:35 +, Keith Whitwell wrote:
> >> So, I decided it would be neat to merge all the changes that have
> >> occurred on the Mesa mainline to the vbo branch where I've started
> >> working
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=9673
Summary: Segment fault when running mesa demo 'texdown' on 64
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=9673
--- Additional Comments From [EMAIL PROTECTED] 2007-01-15 21:23 ---
Creat
13 matches
Mail list logo
