There have been a bunch of seperate reports of memory problems under Dec
OSF/Tru64/Digital Unix. They all seem to boild down to the fact that the
VB->IM->OrFlag and VB->IM->AndFlag variables are being computed incorrectly in
gl_compute_orflag() in vbxform.c.
I'm wondering if there is anyone out there who can easily reproduce any of
these problems can print out the values that are computed for OrFlag and
AndFlag, along with the array of values in VB->IM->Flag from which they are
computed.
An even more adventurous soul might want to look at enabling some of the
printf's in gl_compute_orflag and seeing what might be going wrong.
I'm also interested to see if this is a 64-bit issue that we only see under
Dec OSF, or if it is a compiler-optimization issue specific to that platform
and not really the code's fault -- so could people try disabling optimization
(-O0) and rerunning.
The faults I'm describing are characterized by crashes in either
find_last_3f
or fixup_inputs
I'm interested to hear if people are having crashes in these functions on
non-alpha systems
Keith
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
