public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Georgy Yakovlev" <gyakovlev@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] data/gentoo-news:master commit in: 2019-09-11-cpu_flags_ppc-introduction/
Date: Sun,  7 Jun 2020 23:30:22 +0000 (UTC)	[thread overview]
Message-ID: <1591572597.72de871e6fb59e1e7fb3af51bc6227ad32b0e019.gyakovlev@gentoo> (raw)

commit:     72de871e6fb59e1e7fb3af51bc6227ad32b0e019
Author:     Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
AuthorDate: Sun Jun  7 23:18:31 2020 +0000
Commit:     Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
CommitDate: Sun Jun  7 23:29:57 2020 +0000
URL:        https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=72de871e

2019-09-11-cpu_flags_ppc-introduction.en.txt: new revision

add vsx2 flag information

Signed-off-by: Georgy Yakovlev <gyakovlev <AT> gentoo.org>

 .../2019-09-11-cpu_flags_ppc-introduction.en.txt                   | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/2019-09-11-cpu_flags_ppc-introduction/2019-09-11-cpu_flags_ppc-introduction.en.txt b/2019-09-11-cpu_flags_ppc-introduction/2019-09-11-cpu_flags_ppc-introduction.en.txt
index a4a4ee5..3267fe0 100644
--- a/2019-09-11-cpu_flags_ppc-introduction/2019-09-11-cpu_flags_ppc-introduction.en.txt
+++ b/2019-09-11-cpu_flags_ppc-introduction/2019-09-11-cpu_flags_ppc-introduction.en.txt
@@ -1,7 +1,7 @@
 Title: new CPU_FLAGS_PPC USE_EXPAND
 Author: Georgy Yakovlev <gyakovlev@gentoo.org>
 Posted: 2019-09-11
-Revision: 1
+Revision: 2
 News-Item-Format: 2.0
 Display-If-Keyword: ~ppc
 Display-If-Keyword: ~ppc64
@@ -14,6 +14,7 @@ The flags are:
 
   altivec - Use the AltiVec/VMX instruction set
   vsx - Use the Vector Scalar Extension instruction set
+  vsx2 - Use the Vector Scalar Extension v.2 instruction set
   vsx3 - Use the Vector Scalar Extension v.3 instruction set
 
 Note that CPU_FLAGS_PPC variable is used on ppc and ppc64 architectures.
@@ -29,10 +30,10 @@ This flag needs to be set as:
 
 It's advised to keep 'altivec' USE flag enabled to ensure safe
 migration and compatibility with external repositories.
-'vsx' and 'vsx3' are new flags and no migration necessary.
+'vsx', 'vsx2' and 'vsx3' are new flags and no migration necessary.
 
 To help users enable the correct USE_EXPAND flags PPC support has been
 added to app-portage/cpuid2cpuflags package:
 
-  # emerge -1v >=app-portage/cpuid2cpuflags-7
+  # emerge -1v >=app-portage/cpuid2cpuflags-9
   $ cpuid2cpuflags


             reply	other threads:[~2020-06-07 23:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-07 23:30 Georgy Yakovlev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-16  1:27 [gentoo-commits] data/gentoo-news:master commit in: 2019-09-11-cpu_flags_ppc-introduction/ 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=1591572597.72de871e6fb59e1e7fb3af51bc6227ad32b0e019.gyakovlev@gentoo \
    --to=gyakovlev@gentoo.org \
    --cc=gentoo-commits@lists.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