Hi All,
I finally found the problem on my VMS/Alpha system when running some of
the modes of xlockmore. It appered that the Normal field of the Immediate IM
in VB.C contained rubish after allocation of the immediate. I propose the
following patch to vb.c (Not yet committed since I want your comments first)
*** vb.c;2 Fri Apr 28 16:06:10 2000
--- vb.c;1 Fri Apr 14 07:43:16 2000
***************
*** 272,279 ****
IM->Start = VB_START;
IM->Material = 0;
IM->MaterialMask = 0;
- for (j=0; j<VB_SIZE ; j++ )
- IM->Normal[j][0] = IM->Normal[j][1] = IM->Normal[j][2] = 0.0;
if (MESA_VERBOSE&VERBOSE_IMMEDIATE)
fprintf(stderr, "alloc immediate %d\n", id);
--- 272,277 ----
Maybe the same problem occurs on True64(DECUnix/OSF) on Alpha. Since in
principle the same compiler (but for another OS) is used.
Questions:
-Should I commit this fix for all systems or should I #ifdef VMS it?
-What about the other data-fields in the Immediate. Can they be corrupt too?
Jouk
Ceterum censeo tertium millennium post Christum natum anno MMI incepturum esse
>------------------------------------------------------------------------------<
Jouk Jansen
[EMAIL PROTECTED]
Technische Universiteit Delft tttttttttt uu uu ddddddd
Nationaal centrum voor HREM tttttttttt uu uu dd dd
Rotterdamseweg 137 tt uu uu dd dd
2628 AL Delft tt uu uu dd dd
Nederland tt uu uu dd dd
tel. 31-15-2781536 tt uuuuuuu ddddddd
>------------------------------------------------------------------------------<
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
