add a note about how we should implement this FIXME from the legalizer:

    // FIXME: revisit this when we have some kind of mechanism by which targets
    // can decided legality of vector constants, of which there may be very
    // many.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@25733 91177308-0d34-0410-b5e6-96231b3b80d8

diff --git a/lib/Target/PowerPC/PPCSubtarget.cpp b/lib/Target/PowerPC/PPCSubtarget.cpp
index f43c18d7dfa621c344c3d3781670b009ba3e7102..c7a34280ea7e46d040c4eda90ae4d6738e218227 100644 (file)
--- a/lib/Target/PowerPC/PPCSubtarget.cpp
+++ b/lib/Target/PowerPC/PPCSubtarget.cpp
@@ -1,4 +1,4 @@
-//===- PowerPCSubtarget.cpp - PPC Subtarget Information ---------*- C++ -*-===//
+//===- PowerPCSubtarget.cpp - PPC Subtarget Information -------------------===//
 //
 //                     The LLVM Compiler Infrastructure
 //

diff --git a/lib/Target/PowerPC/README.txt b/lib/Target/PowerPC/README.txt
index 149c2db34e82ba99ca5573ceb9e57cd42ad694fc..3d0736d65ea2d2de9c57cf96a93354b6ff08fbf8 100644 (file)
--- a/lib/Target/PowerPC/README.txt
+++ b/lib/Target/PowerPC/README.txt
@@ -396,3 +396,9 @@ of the GOT on targets with one).
 
 Generate lwbrx and other byteswapping load/store instructions when reasonable.
 
+===-------------------------------------------------------------------------===
+
+Implement TargetConstantVec, and set up PPC to custom lower ConstantVec into
+TargetConstantVec's if it's one of the many forms that are algorithmically
+computable using the spiffy altivec instructions.
+