From: "René Neumann" <lists@necoro.eu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: CPU use flag detection
Date: Sun, 19 May 2013 18:36:26 +0200 [thread overview]
Message-ID: <5198FF8A.4060701@necoro.eu> (raw)
In-Reply-To: <5198F7BE.6050802@gmail.com>
Am 19.05.2013 18:03, schrieb vivo75@gmail.com:
> On 05/19/13 17:47, Alexis Ballier wrote:
>> On Sat, 18 May 2013 22:31:11 -0400
>> "Walter Dnes" <waltdnes@waltdnes.org> wrote:
>>
>> [...]
>>> ...shouldn't "mmxext" be moved out of use.local.desc into use.desc?
>>
>> all the cpu flags should be global IMHO, regardless of how many packages
>> use them: we already mask/unmask them globally on arches where they are
>> irrelevant.
>>
>> Alexis.
>>
> +1
> also +1 they should be easily recognizable as cpu features USE flags, as
> already mentioned recently by someone (sorry could not search)
So this sounds like one of the places, where a USE_EXPAND could really
be correct and worthwhile :).
- René
next prev parent reply other threads:[~2013-05-19 16:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 14:59 [gentoo-dev] CPU use flag detection yac
2013-05-18 4:39 ` [gentoo-dev] " Ryan Hill
2013-05-18 19:14 ` Matt Turner
2013-05-19 2:31 ` Walter Dnes
2013-05-19 15:47 ` Alexis Ballier
2013-05-19 16:03 ` vivo75
2013-05-19 16:36 ` René Neumann [this message]
2013-05-19 16:17 ` Matt Turner
2013-05-22 4:59 ` Ryan Hill
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=5198FF8A.4060701@necoro.eu \
--to=lists@necoro.eu \
--cc=gentoo-dev@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