From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] USE="mmx mmxext sse sse2 ssse3 3dnow 3dnowext"
Date: Tue, 26 May 2009 05:27:34 +0100 [thread overview]
Message-ID: <4E38BD16-0410-4A31-839C-290364A8D735@stellar.eclipse.co.uk> (raw)
Hi there,
I'm always rather reluctant to enable any of these, being unsure
whether my ageing PentiumPro or Pentium 4 CPUs support such features
as 3DNow! (originally an AMD technology) or the advanced SSSSSSSSSE3.
According to this page <http://en.gentoo-wiki.com/wiki/MPlayer>,
however:
You can greatly improve MPlayer's performances (in my experience, by
up to +40%!) by recompiling it with appropriate CPU-related USE
flags.
Moreover:
Note: The mplayer build system will automatically detect your CPU
settings if you allow it. Therefore, the safest thing to do is
enable
all of the optimization USE flags and let the script detect them. If
you disable the use flags, then it will forcibly disable support for
that optimization, and possibly break your build. In other words,
add
mmx mmxext sse sse2 ssse3 3dnow 3dnowext to your USE flags for this
ebuild, and if your box supports it, it will work automatically.
w00t!
Should I enable all these USE flags globally? Will other packages also
fallback safely as mplayer does?
Or should I add all these flags only to /etc/portage/package.use,
allowing mplayer to make full use of the hardware USEs it supports,
but limiting other apps to only those I'm really really confident
about (i.e. "mmx" & that's about it).
Thanks in advance for all suggestions,
Stroller.
next reply other threads:[~2009-05-26 4:27 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 4:27 Stroller [this message]
2009-05-26 4:37 ` [gentoo-user] USE="mmx mmxext sse sse2 ssse3 3dnow 3dnowext" 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
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=4E38BD16-0410-4A31-839C-290364A8D735@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