From: Georgy Yakovlev <gyakovlev@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] PATCH: add CPU_FLAGS_PPC USE_EXPAND
Date: Sat, 31 Aug 2019 00:03:40 -0700 [thread overview]
Message-ID: <20190831070342.28451-1-gyakovlev@gentoo.org> (raw)
Possible users from the tree:
altivec useflag consumers (many)
media libraries (x264, x265, libpng and others.)
also firefox-70[1] will have auto-detection of features but we may want to
prevent automagic optimizations.
cpuid2cpuflags support[2] is ready and and will be merged soon,
so users will have a gentoo-way of setting those flags.
And this patch in github PR[3] format for easy viewing
[1] https://hg.mozilla.org/mozilla-central/rev/252643ff91c5
[2] https://github.com/mgorny/cpuid2cpuflags/pull/13
[3] https://github.com/gentoo/gentoo/pull/12829
next reply other threads:[~2019-08-31 7:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-31 7:03 Georgy Yakovlev [this message]
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
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=20190831070342.28451-1-gyakovlev@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