This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
Jim Wilson <wilson@specifixinc.com> writes: > Mike Stump wrote: >> -fast is very, very small. It just turns on 5-25 other, existing >> flags. There isn't a reason why it could not be contributed. Do >> others want it? It is _good_ for SPEC. > > The set of options that gives best performance on SPEC for a PPC970 is > unlikely to be right for other targets or for other programs. So what > exactly does -fast mean when that is considered? How do we choose > which options to include? Apple probably doesn't want to sacrifice > SPEC performance to make the option useful to others, so perhaps it > makes more sense to rename it to something like -mfast-spec to make it > clear that it is target dependent, and is the set of options that is > known to give best SPEC performance. -fast has to be target specific. And I won't mind adding for some targets a -mfast-spec to make this clear. I just think we should do it the same everywhere. If we support -fast, I'll contribute some Opteron settings ;-) Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Attachment:
pgp00000.pgp
Description: PGP signature
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |