From: Steven Walter <srwalter@yahoo.com>
To: "Manuel A. McLure" <mmt@unify.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Dri-devel] Error compiling glide3 cvs tree from 26 Juli
Date: Thu, 26 Jul 2001 19:23:15 -0500 [thread overview]
Message-ID: <20010726192315.B25074@hapablap.dyn.dhs.org> (raw)
In-Reply-To: <419E5D46960FD211A2D5006008CAC79902E5C3D1@pcmailsrv1.sac.unify.com>
In-Reply-To: <419E5D46960FD211A2D5006008CAC79902E5C3D1@pcmailsrv1.sac.unify.com>; from mmt@unify.com on Thu, Jul 26, 2001 at 03:49:25PM -0700
On Thu, Jul 26, 2001 at 03:49:25PM -0700, Manuel A. McLure wrote:
> Actually, I believe the 3DNow stuff is turned off by default - at least
> configure.in says so. When (a long time ago) I tried to build a
> 3DNow-enabled Glide, I found that I had to modify Makefile.autoconf.am in
> h5/glide3/src to get it to compile. The resulting Glide library would work
> for simple things (like gears), but would hang if I tried something more
> complicated like q3demo (in fact it would hand on the splash screen). As a
> result I am back to non-3DNow Glide. I'd like to see a 3DNow-enabled Glide,
> but I definitely don't have the skills to figure it out myself...
>
> --
> Manuel A. McLure - Unify Corp. Technical Support <mmt@unify.com>
> Zathras is used to being beast of burden to other peoples needs. Very sad
> life. Probably have very sad death, but at least there is symmetry.
You're right. I've examined it some more, and it turns out I'm wrong.
The 3DNow! routines aren't actually used by default.
Just out of curiousity, how much of a speed improvement could one expect
with 3DNow! versus the code used currently?
--
-Steven
In a time of universal deceit, telling the truth is a revolutionary act.
-- George Orwell
parent reply other threads:[~2001-07-27 0:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <419E5D46960FD211A2D5006008CAC79902E5C3D1@pcmailsrv1.sac.unify.com>]
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=20010726192315.B25074@hapablap.dyn.dhs.org \
--to=srwalter@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmt@unify.com \
/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