You're right about the problems with my patch to the test suite.  I was 
trying to separate out my vector-printing changes from the part of the 
patch that I submitted under a separate RFA ("Support Altivec tests on 
Mac OS X"), and didn't do a very good job of it.

I've attached a complete version of our altivec-regs.exp, including the 
parts already submitted under the separate RFA.  I changed "info 
powerpc altivec" to "info vector" and moved the set of hex_vector, 
though I'd argue it's not really all that far away from the usage when 
it's next to the set of decimal_vector, will be even closer if we fix 
the "skip the trailing null" business, and it's handy to have them next 
to each other for comparison.

I wasn't able to test the last part of the patch, about matching the 
vrsave and vscr in the output of "info vector", as our "info vector" 
only lists the vector registers themselves (I'll fix when I covert our 
code to use the new reggroups support in a week or so).