From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-154309-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 25840 invoked by alias); 29 May 2009 00:37:11 -0000
Received: (qmail 25826 invoked by uid 22791); 29 May 2009 00:37:10 -0000
X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Received: from mail-ew0-f157.google.com (HELO mail-ew0-f157.google.com) (209.85.219.157)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 29 May 2009 00:37:06 +0000
Received: by ewy1 with SMTP id 1so6385334ewy.8         for <gcc@gcc.gnu.org>; Thu, 28 May 2009 17:37:03 -0700 (PDT)
Received: by 10.210.88.3 with SMTP id l3mr1717614ebb.88.1243557423575;         Thu, 28 May 2009 17:37:03 -0700 (PDT)
Received: from ?192.168.2.99? (cpc2-cmbg8-0-0-cust61.cmbg.cable.ntl.com [82.6.108.62])         by mx.google.com with ESMTPS id 24sm1426283eyx.13.2009.05.28.17.37.02         (version=SSLv3 cipher=RC4-MD5);         Thu, 28 May 2009 17:37:02 -0700 (PDT)
Message-ID: <4A1F30ED.5080604@gmail.com>
Date: Fri, 29 May 2009 10:12:00 -0000
From: Dave Korn <dave.korn.cygwin@googlemail.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: Piotr Wyderski <piotr.wyderski@gmail.com>
CC: Andrew Pinski <pinskia@gmail.com>, gcc@gcc.gnu.org
Subject: Re: std::exception_ptr on Cygwin
References: <9f8a01cd0905281600n6d452c2h48b5890a3ca45a83@mail.gmail.com> 	 <de8d50360905281605y34fb4eaaq168faa39f45fccc1@mail.gmail.com> <9f8a01cd0905281618vb892b27uc55c565d1a1d2da6@mail.gmail.com>
In-Reply-To: <9f8a01cd0905281618vb892b27uc55c565d1a1d2da6@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
X-SW-Source: 2009-05/txt/msg00676.txt.bz2

Piotr Wyderski wrote:
> Andrew Pinski wrote:
> 
>> i386 did not have atomic locks at all but 486 and above does.
> 
> Thanks, now it is obvious to me. So how should
> I configure my GCC-trunk build? It seems that
> --with-cpu is not enough:

  You need to look closer at the definition of -mcpu, -mtune and -march.  It's
the arch that selects which instructions may be generated, not the tune/cpu
setting which just controls scheduling optimisation and selection of best
instructions between equally available alternatives.  I use "--with-arch=i686
--with-tune=generic".

    cheers,
      DaveK