Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <5.1.0.14.2.20021031120202.01fec528@pop3.cris.com>
X-Sender: rrschulz AT pop3 DOT cris DOT com
Date: Thu, 31 Oct 2002 12:10:24 -0800
To: cygwin <cygwin AT cygwin DOT com>
From: Randall R Schulz <rrschulz AT cris DOT com>
Subject: It's x86
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

Hi,

Since I participated in the confusion about gcc/g++'s interpretation of the 
cpu-type-specific options, I thought I'd post this excerpt from the GCC 
manual page:


        -mcpu=cpu-type
            Tune to cpu-type everything applicable about the
            generated code, except for the ABI and the set of
            available instructions.  The choices for cpu-type are
            i386, i486, i586, i686, pentium, pentium-mmx,
            pentiumpro, pentium2, pentium3, pentium4, k6, k6-2,
            k6-3, athlon, athlon-tbird, athlon-4, athlon-xp and
            athlon-mp.

            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 and athlon are the AMD chips as
            opposed to the Intel ones.

        -march=cpu-type
            Generate instructions for the machine type cpu-type.
            The choices for cpu-type are the same as for -mcpu.
            Moreover, specifying -march=cpu-type implies
            -mcpu=cpu-type.


I don't know how to interpret GCC configuration specifications, so I'll 
just take Chris F.'s exhortation as an indication that the architecture 
setting in the Cygwin build of GCC is i386 and that when the Cygwin 
releases are built, that default is not overridden.

Randy 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/