valgrind upgrade

[Randy MacLeod <Randy.MacLeod@windriver.com>]

I know it's late, 
I know we're weary, 
I know our plans don't include  [1]
valgrind 3.14 which was released recently after 1.5 years of development. 
I believe that some of the M3 valgrind QA results we'ren't very good
so if we're going to try to fix those problems, perhaps
we should be working on the 3.14 release.

I've reviewed and updated the patches but so far I've only built for qemux86. 
The other qemus are building overnight. 

If someone wants to test basic runtime functions and 
better still run the ptests, that would be great.

The important bits of the release notes IMO:

* More than 100 bugs fixed.

* Valgrind is now buildable with link-time optimisation (LTO).  A new
  configure option --enable-lto=yes allows building Valgrind with LTO.  If the
  toolchain supports it, this produces a smaller/faster Valgrind (up to 10%).
  Note that if you are doing Valgrind development, --enable-lto=yes massively
  slows down the build process.
-- I haven't added support for that option yet. A 10% performance boost
   is hard to turn down but we'd need to understand the build impact.

* The new option --keep-debuginfo=no|yes (default no) can be used to retain
  debug info for unloaded code.  This allows saved stack traces (e.g. for
  memory leaks) to include file/line info for code that has been dlclose'd (or
  similar).  See the user manual for more information and known limitations.
-- sounds like it should be a default but I haven't added it yet.

Full release notes:
http://valgrind.org/docs/manual/dist.news.html

../Randy

[1] With apologies for the first line to Kenny Rogers.