From: Daniel Iliev <daniel.iliev@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] USE="mmx mmxext sse sse2 ssse3 3dnow 3dnowext"
Date: Thu, 28 May 2009 13:17:35 +0300 [thread overview]
Message-ID: <20090528131735.10e3b3ce@ilievnet.com> (raw)
In-Reply-To: <fecdbac60905271423v52ce71fi61fb724b1da3d2e7@mail.gmail.com>
On Thu, 28 May 2009 00:23:52 +0300
"Arttu V." <arttuv69@gmail.com> wrote:
> On 5/27/09, Wyatt Epp <wyatt.epp@gmail.com> wrote:
> > Reading this thread, though, it seems like it would be useful to
> > have a FEATURES=cpudetection for Portage.
>
> Congratulations, it's already there! Sort of. -march=native ;)
>
Not the same thing. "-march=" instructs gcc to produce a binary
designed to run only on the given CPU architecture, while
USE flags instruct the build system to include or not support for a
given feature. Think of the USE flags "this" and "that" as shortcuts to
"./configure --enable-this --disable-that".
So, for example mplayer could be a binary which can take advantage (or
not) of SSSE3 and is designed to run only (or not) on core2.
P.S.
And what's next - feature like:
FEATURES="do_the_best_system_ever"
where "do_the_best_system_ever" is a shorthand for:
detect_best_cflags
detect_best_cxxflags
detect_best_ldflags
detect_best_uselags
Sounds good and it's not against Gentoo philosophy - the end user has
the choice to use this feature or not. Any volunteers for the
implementation? Oh, wait! Somebody define "best", please! :)
--
Best regards,
Daniel
next prev parent reply other threads:[~2009-05-28 10:17 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
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 [this message]
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=20090528131735.10e3b3ce@ilievnet.com \
--to=daniel.iliev@gmail.com \
--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