Sender: nate AT cartsys DOT com
Message-ID: <35DF0F31.E575AD3D@cartsys.com>
Date: Sat, 22 Aug 1998 11:34:25 -0700
From: Nate Eldredge <nate AT cartsys DOT com>
MIME-Version: 1.0
To: Vic <tudor AT cam DOT org>
CC: djgpp AT delorie DOT com
Subject: Re: DJGPP and MMX
References: <3 DOT 0 DOT 3 DOT 16 DOT 19980812100524 DOT 3777d674 AT bbs DOT frc DOT utn DOT edu DOT ar> <35D362BC DOT 87CC610A AT sprynet DOT com> <35D38A0D DOT 2B91 AT cam DOT org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

Vic wrote:
> 
> Ishpeck wrote:
> >
> > That's a good one.  As far as I know, It doesn't... but, that's just
> > an assumption, not fact... tell me when you firgure it out, if you don't
> > mind.
> 
> yes, I don't think inline asm does that either, but there are ways to
> use MMX of course. one is to manually input the bytecodes. another is to
> use NASM which supports MMX instructions

I believe recent versions of GAS understand MMX opcodes (though I think
it may generate the wrong one for PADD due to a bug).  Of course, the
compiler itself knows nothing about MMX.  There is, however, a patch
available which adds MMX support to GCC.  An announcement was posted
here some time ago; search the archives.
-- 

Nate Eldredge
nate AT cartsys DOT com