X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <49D139C5.90004@gmail.com> Date: Mon, 30 Mar 2009 22:29:41 +0100 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: gcc4: missing atomic builtins? References: <49CD325C DOT 5030109 AT users DOT sourceforge DOT net> <49CF2163 DOT 3060602 AT gmail DOT com> <416096c60903290155g34878e17gf3311de983a659be AT mail DOT gmail DOT com> <20090330084336 DOT GO12738 AT calimero DOT vinschen DOT de> In-Reply-To: <20090330084336.GO12738@calimero.vinschen.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Corinna Vinschen wrote: > The last i586 was built in 1999 and had a 300 MHz clock rate. The i686 > has been introduced in 1995 and in 1999 the P3 had a minimum clock rate > of 450 MHz. > > I don't think we really need a default compiler and a default installation > sticking to the old i586 design any longer. And, btw, is there any > Linux distro still using a i586 compiler? > > If there are really still i586 users out there, hey, it's all available > in sources. Right. I'll set i686 as the default arch. If anyone really does want to run Cygwin on an i586, they will be SOL, as it's entirely possible they won't be able to run the DLL or anything because everything in the distro will use instructions that their CPU doesn't handle; they'll have to stick with 1.5, or cross-boostrap the entire distro themselves starting from scratch. To Andy's previous post: I think the documentation suggests we want to use -mtune=generic for the best results across the broadest range of CPUs. At the moment, generic and i686 are basically the same, but since -march sets the *minimum* level CPU whereas mtune is aimed at the *typical* CPU (since it will only pessimise, not break anything if incorrct) I think it makes sense to anchor -march and let -mtune float. cheers, DaveK -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/