X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: Subject: RE: [ANNOUNCEMENT] New experimental package: gcc4-4.3.0-1 Date: Wed, 10 Sep 2008 19:16:31 +0100 Message-ID: <007b01c91371$59dbd0a0$9601a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 NightStrike wrote on 10 September 2008 18:54: > On Wed, Sep 10, 2008 at 7:15 AM, Dave Korn wrote: >> Well, here it is at last. Experimental test release of GCC 4 series >> for Cygwin. Please be aware that this is highly experimental; anything > > Dave, > > I've been building and releasing gcc 4.3 and gcc 4.4 toolchains to > cross compile from cygwin to Win64 for I guess a year now. Would you > (or cygwin in general) be interested in that as another package to > offer? (ie, offering the gcc4 cross compiler) Well, the slightly-longer-but-not-very-long term plan is to remove -mno-cygwin and package up a completely separate mingw cross-compiler, so it would make a lot of sense to have either a bi-arch capable cross-compiler, or offer a 64-bit-targeted version alongside the 32-bit-targeted one. Is there much in the way of local patching needed? (I've seen you and Kai working on the win64 target on the gcc-l, but I haven't been following very closely.) cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/