From: Georgy Yakovlev <gyakovlev@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Georgy Yakovlev <gyakovlev@gentoo.org>
Subject: Re: [gentoo-dev] [PATCH 1/2] profiles/desc: descriptions for CPU_FLAGS_PPC use_expand
Date: Sat, 31 Aug 2019 00:19:45 -0700 [thread overview]
Message-ID: <d9899870-1146-ad1e-7f84-c17df1c573c5@gentoo.org> (raw)
In-Reply-To: <422b3e12c06bc3c25c6cee74593dfce3dc39b8a8.camel@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 812 bytes --]
On 8/30/19 11:11 PM, Michał Górny wrote:
> On Sat, 2019-08-31 at 00:03 -0700, Georgy Yakovlev wrote:
<snip>
>> +altivec - Use the AltiVec instruction set
>> +vsx - Use the Vector Scalar Extension instruction set (POWER7 and later)
>> +vsx3 - Use the Vector Scalar Extension v.3 instruction set (POWER9 and later)
>
> Do all those flags have real use cases in ::gentoo? I'd really prefer
> not having more 'unused flag' warnings ;-).
>
yeah, I have mentioned possible users above and there are plenty I
haven't identified yet. patches to ebuilds will follow, I promise =)
for example x264 if built with proper flags gives a noticeable boost,
(at least 2x at encoding), totally worth it.
ppc will not have a lot of flags like on arm or x86, maybe a couple
more, but that's it for now.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-08-31 7:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-31 7:03 [gentoo-dev] PATCH: add CPU_FLAGS_PPC USE_EXPAND Georgy Yakovlev
2019-08-31 7:03 ` [gentoo-dev] [PATCH 1/2] profiles/desc: descriptions for CPU_FLAGS_PPC use_expand Georgy Yakovlev
2019-08-31 7:11 ` Michał Górny
2019-08-31 7:19 ` Georgy Yakovlev [this message]
2019-08-31 7:29 ` Michał Górny
2019-08-31 7:44 ` Georgy Yakovlev
2019-08-31 7:03 ` [gentoo-dev] [PATCH 2/2] profiles: Add CPU_FLAGS_PPC to USE_EXPAND Georgy Yakovlev
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=d9899870-1146-ad1e-7f84-c17df1c573c5@gentoo.org \
--to=gyakovlev@gentoo.org \
--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