Keith Whitwell wrote:
>
> Holger Waechtler wrote:
> >
> > Hi Ralph,
> >
> > 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).
> >
> > 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.
> >
> > If you compiled them all into the library, void gl_init_all_x86_asm (void)
> > tests, which additional capabilities the cpu supports and hooks in the
> > right code.
>
> Why can't we just compile all of them in (on x86 systems)
I believe that you can, as long as your binutils can cope.
> and do the
> test at runtime to decide which ones to activate?
Again, I read Holger's last paragraph to indicate that that is
what happens (correct me if I'm wrong).
Regards,
--Adam
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
