fixed in current Mesa, just needs to be merged before release now.

It would be nice to get Mesa 6.1 merged and pull this fix in if necessary.  I
don't think I can do it because of my very limited connectivity right now.  I'll
check back on this bug tomorrow, and I *might* be able to do it then, but it
would be much better if someone else could handle this.

Mesa 6.1 has been merged and this fix has been brought over.
Closing.

This needs to happen for ARM too. I'm unsure whether __arm32__ or __arm__ is
more correct.

(In reply to comment #4)
> This needs to happen for ARM too. I'm unsure whether __arm32__ or __arm__ is
> more correct.

If we are to include this in the X.Org release, we will need to know ASAP which
one is correct.

All I can say is that we know this is required for arm32, and we're not sure
about anything else (e.g., arm in general) because nobody using arm64 has
brought up the issue. I don't know of anyone with arm64 to ask about it, either.
The safe way would probably be to do the thing we know is correct (__arm32__)
rather than the thing that may or may not work for everyone (__arm__).

i say (__arm__) is correct; i can't imagine arm32 would use IEEE floating point
and arm64 would not.  all five arm64 users are welcome to give me a beatdown if
that turns out not to be the case.

Fixed in Mesa CVS (Added test for __arm__ to mesa/src/main/imports.h).

Added __arm__ from Mesa CVS.
Closing.

__sh__ has same problem. Please add __sh__ too.

the bug that will not die...

applied to mesa head and 6.4 branch, closing.  will show up in the monolith on
the next Mesa import.