X-Spam-Check-By: sourceware.org
Message-ID: <03a901c79238$63b293e0$0200a8c0@AMD2500>
From: "Aaron Gray" <angray AT beeb DOT net>
To: "Aaron W. LaFramboise" <aaronpurpleleaf4 AT aaronwl DOT com>
Cc: <cygwin AT cygwin DOT com>, <gcc AT gcc DOT gnu DOT org>
References: <2b2c01c78fa5$d94a27c0$0200a8c0 AT AMD2500> <01f001c78fc6$c916ce00$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <463DDE7F DOT 5010105 AT cwilson DOT fastmail DOT fm> <463EDE36 DOT 1020807 AT aaronwl DOT com> <005601c790b9$52c5e940$0200a8c0 AT AMD2500> <464178E3 DOT 10108 AT aaronwl DOT com>
Subject: Re: Successful build of GCC 4.2.0 RC3 on latest Cygwin snapshot 20070427
Date: Wed, 9 May 2007 13:48:48 +0100
MIME-Version: 1.0
Content-Type: text/plain; 	format=flowed; 	charset="iso-8859-1"; 	reply-type=response
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

> Aaron Gray wrote:
> 
>>> One issue that might affect many some is that COM doesn't work. 
>>> <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27067> has a patch that 
>>> is pending review I guess, but probably won't go into 4.2.
> 
>> Does this effect XPCOM meaning Mozilla and friends will not compile ?
> 
> It is triggered anywhere multiple inheritance is combined with stdcall. 
>  Since I believe XPCOM uses stdcall on Windows (but "cdecl" on other 
> targets), I believe the answer here is 'Yes, Mozilla will not compile.'

But its fine on Unix platforms, that is good.

I am not sure if MinGW will/is used to compile Mozilla on Windows anyway.
 
> I think it's likely that mingw.org will include this fix in their own 
> releases of 4.2, which is probably a bad thing, as it makes the need to 
> get this fix into official GCC sources seem less urgent.  A lot of GCC 
> patches for Windows-related issues tend to stall for a long time in this 
> state; I'm not really sure why.

Yes, this is perplexing.

Aaron


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