public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: Jon Ellis <jje@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] The SIMD debacle
Date: Tue, 30 Sep 2003 12:21:26 -0400	[thread overview]
Message-ID: <1064938885.3257.99.camel@localhost> (raw)
In-Reply-To: <28C2D7E4-F344-11D7-A570-0003934489D0@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 939 bytes --]

On Tue, 2003-09-30 at 08:46, Jon Ellis wrote:
> Can someone explain the sse / 3dnow! situation to me?
> 
> My understanding is that most modern intel and amd chips supprt sse, 
> but only amd support 3dnow! Is this correct? Why would someone with a 
> pentium 4 box have 3dnow in their use flags?

Pentium 3 - sse
Pentium 4 - sse/sse2
Athlon - 3dnow
AthlonXP - 3dnow/sse

> Does anyone point me a ebuilds that correctly handle this stuff? It 
> would be most useful to understand how protect users from themselves 
> and reduce the number 'invalid instruction' bugs filed against 
> libvorbis!

If you need some help with this ebuild, I'll gladly help, since I think
I might have been the one that caused you all the headache in the first
place.

> 
> Thanks
> 
> j.
> 
> 
> --
> gentoo-dev@gentoo.org mailing list
-- 
Chris Gianelloni
Developer, Gentoo Linux
Games Team

Is your power animal a pengiun?

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-09-30 16:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-30 12:46 [gentoo-dev] The SIMD debacle Jon Ellis
2003-09-30 12:57 ` Paul de Vrieze
2003-09-30 14:37 ` Jon Portnoy
2003-09-30 16:21 ` Chris Gianelloni [this message]
2003-09-30 19:35   ` David Holm

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=1064938885.3257.99.camel@localhost \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=jje@gentoo.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