2019-09-11-cpu_flags_ppc-introduction: new item

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

1 files changed, 38 insertions, 0 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
new file mode 100644
index 0000000..a4a4ee5
--- /dev/null
+++ b/2019-09-11-cpu_flags_ppc-introduction/2019-09-11-cpu_flags_ppc-introduction.en.txt
@@ -0,0 +1,38 @@
+Title: new CPU_FLAGS_PPC USE_EXPAND
+Author: Georgy Yakovlev <gyakovlev@gentoo.org>
+Posted: 2019-09-11
+Revision: 1
+News-Item-Format: 2.0
+Display-If-Keyword: ~ppc
+Display-If-Keyword: ~ppc64
+Display-If-Keyword: ppc
+Display-If-Keyword: ppc64
+
+
+A new set of CPU_FLAGS_PPC USE_EXPAND flags has been added.
+The flags are:
+
+  altivec - Use the AltiVec/VMX instruction set
+  vsx - Use the Vector Scalar Extension 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.
+
+In order to transition to new set of flags, if the following flag was
+was present:
+ 
+  USE="altivec"
+
+This flag needs to be set as:
+
+  CPU_FLAGS_PPC="altivec"
+
+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.
+
+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
+  $ cpuid2cpuflags