From: Jeff Garzik <jgarzik@pobox.com>
To: gcc@gcc.gnu.org
Subject: MMX regs and GCC
Date: Thu, 30 Sep 1999 18:02:00 -0000 [thread overview]
Message-ID: <37D625F7.C5CF2FE8@pobox.com> (raw)
Message-ID: <19990930180200.day-fvU_TdvNzwf_HGvCNifkYz3QsIA9p2rjE3sHIhY@z> (raw)
Dumb question... can the ia32 MMX regs be used to ease register
pressure on that platform? No SIMD, just store a single integral <= 64
bits in the available regs.
Thanks,
Jeff
--
Custom driver development | Never worry about theory as long
Open source programming | as the machinery does what it's
| supposed to do. -- R. A. Heinlein
next reply other threads:[~1999-09-30 18:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-08 2:03 Jeff Garzik [this message]
1999-09-30 18:02 ` Jeff Garzik
[not found] <199909081748.KAA22465@netcom1.netcom.com>
1999-09-08 13:30 ` Jeff Garzik
1999-09-08 13:42 ` Ben Combee
1999-09-08 13:50 ` Jeff Garzik
1999-09-10 8:24 ` Jamie Lokier
1999-09-30 18:02 ` Jamie Lokier
1999-09-30 18:02 ` Jeff Garzik
1999-09-30 18:02 ` Ben Combee
1999-09-11 16:11 ` Marc Lehmann
1999-09-30 18:02 ` Marc Lehmann
1999-09-30 18:02 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37D625F7.C5CF2FE8@pobox.com \
--to=jgarzik@pobox.com \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).