Messages in this thread | | | From | "H. Peter Anvin" <> | Subject | Re: Algorithm for CPU_X86 | Date | 3 Jun 2002 22:19:12 -0700 |
| |
Followup to: <20020604031840.GA4289@werewolf.able.es> By author: "J.A. Magallon" <jamagallon@able.es> In newsgroup: linux.dev.kernel > > Following with the cpu selection changes, setting the flags controlled > by the various CPU_X86_xxxx can be a real mess. > > But, I have ralized that those CPU_X86 flags can be logically split in > two groups: features (TSC,MMX,3DNOW) and bugfixes (PPRO_FENCE) (or perhaps > more, it is just a first thought...). >
Don't forget optimizations. It's a big difference between "optimize for" and "require" -- consider gcc, which have -mcpu= and -march= respectively for the two.
-hpa -- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |