delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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: | <20050807050059.50215.qmail@web31508.mail.mud.yahoo.com> |
Date: | Sat, 6 Aug 2005 22:00:59 -0700 (PDT) |
From: | "James R. Phillips" <antiskid56-cygwin AT yahoo DOT com> |
Reply-To: | antiskid56-cygwin AT yahoo DOT com |
Subject: | gcc 4.0 on cygwin |
To: | cygwin AT cygwin DOT com |
MIME-Version: | 1.0 |
Continuing discussions regarding gcc 3.4 beg the question of when we are going to start work on gcc 4.0 for cygwin. Is there anything holding us back? As I understand it, Debian will skip over gcc 3.4 and move from 3.3 to 4.0 as its standard compiler for Etch. This gives me some confidence that gcc 4.0 is going to be very thoroughly vetted over the next 18 to 24 months. I wonder if the time we are spending on gcc 3.4 might be better spent on what will probably be a better tested and better performing compiler. No disrespect is intended for the massive amount of work already done on gcc 3.4. I just wonder if it isn't time to move on? -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |