This is the mail archive of the
mailing list for the GCC project.
RE: GCC 4.1.0 Released
- From: "Meissner, Michael" <michael dot meissner at amd dot com>
- To: "Mark Mitchell" <mark at codesourcery dot com>, "H. J. Lu" <hjl at lucon dot org>
- Cc: "Steven Bosscher" <stevenb dot gcc at gmail dot com>, gcc-patches at gcc dot gnu dot org, "Richard Guenther" <richard dot guenther at gmail dot com>, gcc at gcc dot gnu dot org
- Date: Tue, 7 Mar 2006 12:59:33 -0500
- Subject: RE: GCC 4.1.0 Released
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
From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of
Sent: Wednesday, March 01, 2006 8:22 PM
To: H. J. Lu
Cc: Steven Bosscher; email@example.com; Richard Guenther;
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.
(650) 331-3385 x713