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: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com From: Chris Faylor Date: Sun, 9 Jul 2000 01:41:05 -0400 To: cygwin-apps AT sourceware DOT cygnus DOT com Subject: Re: processor compatibility when building packages Message-ID: <20000709014105.A12976@cygnus.com> Mail-Followup-To: cygwin-apps AT sourceware DOT cygnus DOT com References: <39675070 DOT 9C41CB2E AT ece DOT gatech DOT edu> <200007090141 DOT VAA03096 AT envy DOT delorie DOT com> <39680072 DOT 8E859850 AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <39680072.8E859850@ece.gatech.edu>; from cwilson@ece.gatech.edu on Sun, Jul 09, 2000 at 12:32:50AM -0400 On Sun, Jul 09, 2000 at 12:32:50AM -0400, Charles Wilson wrote: >DJ Delorie wrote: >>>Does cygwin only officially work on i686, so that it is okay to use >>>these routines and break compatibility with older systems? >> >>Please do not break older systems. > >My inclination was to maintain as much compatibility as possible. >However, I was confused since the official platform triple is now >i686-pc-cygwin, not i386-pc-cygwin or ix86-pc-cygwin. It *USED* to be >i386- but was changed sometime in the last six months. Why? What does >the new triple signify? The last time I asked about this, I was informed that using the i686-pc-cygwin triple does not break anything. You still have to use special compiler flags to create code that is unusable on older CPUs. I've sent mail to a gcc engineer to confirm this but he's probably getting sick of me asking this question. In general, I think we'll probably get fewer questions using i686 than i386. Since the i?86-pc-cygwin directory is disappearing, this may not be as much of an issue. cgf