On Thu, Oct 04, 2012 at 06:33:33PM +0200, Gunther Nikl wrote: > 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.
Well as I said, it is pretty latent, and most people never have noticed it. It really depends on what the options are whether you run into the problem. I added more verbose debug information to the patches for -mdebug=reg to verify what options are being set, etc. Hopefully these patches can finally get accepted. -- Michael Meissner, IBM 5 Technology Place Drive, M/S 2757, Westford, MA 01886-3141, USA meiss...@linux.vnet.ibm.com fax +1 (978) 399-6899
