On 7 Jun, Holger Waechtler wrote:
> Hi Ralph,
Thanks for the response! I'm having another go now that the new asm
stuff has moved into the main branch.
> The asm_???.c /.h /.S files are not used at this time. Take a look into
> the files in src/X86 instead (prefer the experimental-1 CVS branch,
> there are the 3Dnow related things in this folder, too).
I notice the 3Dnow directory is empty now. This is obsolete as well?
> It should work once like this:
>
> For a x86 target, cmopile with -DUSE_X86_ASM -DUSE_MMX_ASM
> -DUSE_3DNOW_ASM. Your configure script has to test (perhaps by compiling
> one of the x86/MMX/3dnow files), if the binutils know all necessairy
> commands. If not, you should not define the relating USE_XXX_ASM.
Ah, so it's to be USE_MMX_ASM. Better name, I agree.
This is more or less what we do, except we're adding -DMMX. This is
causing the problems I think. src/blend.c uses gl_mmx_blend_transparency
from asm_mmx.c if -DMMX, and as I've said asm_mmx.c is missing the
headers and doesn't compile. I've removed it from our Makefile.in, but
we still get an unresolved symbol that way.
I tested this code with the pulsar demo and it seemed to work correctly.
Also gave a ~20% speedup. Maybe this should be translated into the X86
directory? (why not x86 btw? X86 makes me think XFree86.)
However, looking at Make-config, I don't see -DMMX or -DUSE_MMX_ASM
anywhere, nor in the lower-level Makefiles. Am I missing something?
We can work around all this by disabling mmx entirely (and I guess we
won't be missing anything :) but it would be nice to get things cleaned
up.
Cheers,
-ralph
(and thanks for all the 3Dnow support!)
---
[EMAIL PROTECTED]
information design? what's that?
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
