When -mtune=generic was added, it was expected that it would go into the 4.2 GCC release, since it clearly missed the 4.1 window for new features. As desirable for both AMD and Intel that the new behavior be propagated, I feel like Mark that it should wait for GCC 4.2, since it clearly is a new feature. However, if it does go in, it will be for the good, but I'm not pressing for it.
Note, in this case, I am not officially speaking for AMD (though I have taken part in discussions on our side about adding the generic tuning feature). -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Mitchell Sent: Wednesday, March 01, 2006 8:22 PM To: H. J. Lu Cc: Steven Bosscher; [EMAIL PROTECTED]; Richard Guenther; gcc@gcc.gnu.org Subject: Re: GCC 4.1.0 Released H. J. Lu wrote: > You are comparing apply with orange. If a user uses -O2, he/she will > see much more than that. We can argue about that, but I don't think so. I'm comparing a user can achieve without the patch with the performance they can achieve with the patch. On all chips, for all time, users have been expected to specify their target CPU in order to get good performance. It's swell that GCC 4.2 will work better by default on IA32, but that's not a compelling argument for a backport. -- Mark Mitchell CodeSourcery [EMAIL PROTECTED] (650) 331-3385 x713
