On Thu, Mar 8, 2012 at 1:17 PM, Michael Meissner
> David noticed that I set default_cpu twice in my previous patch. This patch
> fixes that, and also updates the ChangeLog message to indicate fixing some
> tests for using >= 0 instead of > 0, since processor 0 is a valid index. I've
> bootstrapped both 4.7 and 4.8 with this new patch. Is it ok to install? As I
> said, in the original message, we would like to install in 4.7 rather than
> waiting for 4.7.1.
> 2012-03-08 Michael Meissner <meiss...@the-meissners.org>
> * config/rs6000/linux64.h (OPTION_TARGET_CPU_DEFAULT): Do not
> redefine to be NULL if the current bit-size is different from the
> configured bit-size.
> * config/rs6000/rs6000.c (rs6000_option_override_internal): If the
> cpu is defaulted, use PROCESSOR_DEFAULT and PROCESSOR_DEFAULT64 to
> set the default tuning. Add asserts to make sure the cpu and tune
> indexes are defined. Fix tests for cpu/tune index to use >= 0 to
> test whether the index is set, instead of > 0.
> (rs6000_file_start): Do not reset the default cpu if the current
> bit-size is different from the configured bit-size.
This patch is okay.
Let's try this on trunk and hopefully it can be included in the