public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] USE="mmx mmxext sse sse2 ssse3 3dnow 3dnowext"
Date: Tue, 26 May 2009 09:34:32 +0100	[thread overview]
Message-ID: <2B514C4A-E484-47B2-8B3B-3DF07A2D9165@stellar.eclipse.co.uk> (raw)
In-Reply-To: <200905260827.21663.volkerarmin@googlemail.com>


On 26 May 2009, at 07:27, Volker Armin Hemmann wrote:
>> ...
>> I did think that. But with other instructions adopted by the other
>> manufacturer (eg. Intel adopted the amd64 architecture, I think?) it
>> seemed odd that a set of instructions would be ignored so long.
>
> because 3dnow is/was very unimportant for intel- but Intel couldn't  
> compete
> without AMD64. So they had to licence it. 3dnow and SSE have a lot  
> of commands
> in common/similar commands anyway so it doesn't really matter from  
> Intels POV.

Completely OT now, but I seem to have a recollection that they have a  
cross-licensing agreement which covers stuff like this without further  
royalties.

Thanks for your help & the interesting discussion,

Stroller.



  reply	other threads:[~2009-05-26  8:35 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-26  4:27 [gentoo-user] USE="mmx mmxext sse sse2 ssse3 3dnow 3dnowext" Stroller
2009-05-26  4:37 ` Adam Carter
2009-05-26  4:59   ` Volker Armin Hemmann
2009-05-26  4:37 ` Volker Armin Hemmann
2009-05-26  5:00   ` Stroller
2009-05-26  5:10     ` Volker Armin Hemmann
2009-05-26  6:15       ` Stroller
2009-05-26  6:27         ` Volker Armin Hemmann
2009-05-26  8:34           ` Stroller [this message]
2009-05-26 14:31     ` Daniel Iliev
2009-05-26 21:07       ` Stroller
2009-05-27  0:47         ` Daniel Iliev
2009-05-27  8:14           ` Stroller
2009-05-27 10:00             ` Daniel Iliev
2009-05-27 12:14               ` Stroller
2009-05-27 19:57                 ` Wyatt Epp
2009-05-27 20:04                   ` Volker Armin Hemmann
2009-05-27 20:09                     ` Alan McKinnon
2009-05-27 20:40                       ` Wyatt Epp
2009-05-27 20:47                         ` Volker Armin Hemmann
2009-05-27 21:04                         ` Mike Edenfield
2009-05-27 21:12                           ` Alan McKinnon
2009-05-27 23:00                       ` Adam Carter
2009-05-27 20:08                   ` Ward Poelmans
2009-05-27 21:04                     ` Mike Edenfield
2009-05-27 21:23                   ` Arttu V.
2009-05-28 10:17                     ` Daniel Iliev
2009-05-28 19:13                       ` Stroller
2009-05-28 20:08                         ` Ward Poelmans
2009-05-28 20:19                           ` Stroller
2009-05-28 20:27                             ` Ward Poelmans
2009-05-28 20:38                               ` Stroller
2009-05-29  5:30                             ` Graham Murray
2009-05-29  6:36                               ` Volker Armin Hemmann
2009-05-29  6:55                               ` Volker Armin Hemmann
2009-05-29 15:25                                 ` Mike Edenfield
2009-05-29  7:51                             ` Neil Bothwick
2009-05-26 22:20       ` KH
2009-05-26 22:26         ` KH
2009-05-26 22:32         ` Alan McKinnon
2009-05-26 13:26 ` [gentoo-user] " James

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=2B514C4A-E484-47B2-8B3B-3DF07A2D9165@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --cc=gentoo-user@lists.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