X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Message-ID: <b609cb3b0809101121w1f187749kfc494a3938de6bfd@mail.gmail.com>
Date: Wed, 10 Sep 2008 14:21:38 -0400
From: NightStrike <nightstrike AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] New experimental package: gcc4-4.3.0-1
Cc: "Kai Tietz" <Kai DOT Tietz AT onevision DOT com>,
   "Kai Tietz" <ktietz70 AT googlemail DOT com>
In-Reply-To: <007b01c91371$59dbd0a0$9601a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <announce.001001c91336$91e70d10$9601a8c0 AT CAM DOT ARTIMI DOT COM> 	 <b609cb3b0809101053g69acb08cra7d2db7c6d2a83a6 AT mail DOT gmail DOT com> 	 <007b01c91371$59dbd0a0$9601a8c0 AT CAM DOT ARTIMI DOT COM>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

On Wed, Sep 10, 2008 at 2:16 PM, Dave Korn <dave DOT korn AT artimi DOT com> wrote:
> NightStrike wrote on 10 September 2008 18:54:
>
>> On Wed, Sep 10, 2008 at 7:15 AM, Dave Korn <dave DOT korn AT artimi DOT YOW> 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.

Multilib support is there.  The only holdup is getting people to agree
on pathnames for the 32-bit and 64-bit variant of lib directories (ie,
use lib and lib32, or lib and lib64... I think someone even suggested
no lib and just lib32 and lib64....)  It's annoying sometimes when
it's that kind of stuff that holds up progress, but there you have it.

>  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.)

One of our design goals was to have no local patch needed ever.  So
currently, everything is always pushed upstream as soon as we find a
fix.

--
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/