www.delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm |
Sender: | cygwin-apps-owner AT sourceware DOT cygnus DOT com |
List-Subscribe: | <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin-apps/> |
List-Post: | <mailto:cygwin-apps AT sources DOT redhat DOT com> |
List-Help: | <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs> |
Delivered-To: | mailing list cygwin-apps AT sources DOT redhat DOT com |
Message-ID: | <8D00C32549556B4E977F81DBC24E985D40FFD3@crtsmail1.technol_exch.corp.riotinto.org> |
From: | "Billinghurst, David (CRTS)" <David DOT Billinghurst AT riotinto DOT com> |
To: | "'cygwin-apps AT cygwin DOT com'" <cygwin-apps AT cygwin DOT com> |
Subject: | RE: processor compatibility when building packages |
Date: | Sun, 14 Oct 2001 01:01:39 -0000 |
MIME-Version: | 1.0 |
X-Mailer: | Internet Mail Service (5.5.2653.19) |
From the fine manual http://gcc.gnu.org/onlinedocs/gcc-3.0.1/gcc_3.html#SEC35 -mcpu=cpu-type Assume the defaults for the machine type cpu-type when scheduling instructions. The choices for cpu-type are `i386', `i486', `i586', `i686', `pentium', `pentiumpro', `k6', and `athlon' While picking a specific cpu-type will schedule things appropriately for that particular chip, the compiler will not generate any code that does not run on the i386 without the `-march=cpu-type' option being used. `i586' is equivalent to `pentium' and `i686' is equivalent to `pentiumpro'. `k6' is the AMD chip as opposed to the Intel ones.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |