Michael Meissner schrieb: > On Tue, Oct 02, 2012 at 10:13:25AM +0200, Gunther Nikl wrote: >> Michael Meissner wrote: >>> Segher Boessenkool asked me on IRC to break out the fix in the last change. >>> This patch is just the change to set the default options if the user did not >>> use -mcpu=<xxx> and the compiler was not configured with --with-cpu=<xxx>. >>> Here are the patches. >> Which GCC releases are affected by this bug? > > All of them.
So this bug is as old as the rs6000 port has PowerPC support? Then GCC 2.95 is also affected? > Now, in general users don't see this bug, because distribution maintainers > usually build with an explicit --with-cpu= option, which sets the default > CPU in case the user did not use -mcpu=<xxx> on the command line. If neither > option was used, the default "powerpc" or "powerpc64" is usually good enough. I am not a distribution user. I have a private PPC port which I always build without an explicit --with-cpu= option. This option seemed to be redundant with PROCESSOR_DEFAULT and TARGET_DEFAULT in the target config file. I will alter my build procedure. Regards, Gunther
