Relax requirement from VFP3 to VFP2 where possible.

src/platform-linux.cc

Index: src/platform-linux.cc
diff --git a/src/platform-linux.cc b/src/platform-linux.cc
index 9e4dd8b97f31d98d0377eef46b593de7f37edf80..5da9000267d394ca318158af089ec72e51884071 100644
--- a/src/platform-linux.cc
+++ b/src/platform-linux.cc
@@ -132,6 +132,9 @@ bool OS::ArmCpuHasFeature(CpuFeature feature) {
   // facility is universally available on the ARM architectures,
   // so it's up to individual OSes to provide such.
   switch (feature) {
+    case VFP2:
+      search_string = "vfp";

[Rodolph Perfetta, 2012/07/25 10:59:54]

this will match the vfpv3 string since when they differ the search_string will
have reach '\0'.

Maybe put "vfp "

[Yang, 2012/07/25 12:09:32]

since VFP3 implies VFP2, wouldn't this be fine? I'm concerned that if the
cpuinfo string happens to end with "vfp", "vfp " wouldn't match.

+      break;
     case VFP3:
       search_string = "vfpv3";
       break;