Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Mon, 14 Jun 1999 21:15:37 -0400
To: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>
Cc: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: Tonight's snapshot
Message-ID: <19990614211537.D3801@cygnus.com>
References: <19990614191043 DOT A3693 AT cygnus DOT com> <199906142216 DOT RAA18739 AT mercury DOT xraylith DOT wisc DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <199906142216.RAA18739@mercury.xraylith.wisc.edu>; from Mumit Khan on Mon, Jun 14, 1999 at 05:16:21PM -0500

I don't think I want to break binary compatibility quite yet.  I agree
that it would be nice to ensure that things are working correctly.

I'd be grateful to anyone who could look into this.

cgf

On Mon, Jun 14, 1999 at 05:16:21PM -0500, Mumit Khan wrote:
>Chris Faylor <cgf AT cygnus DOT com> writes:
>> I hope that the snapshots are getting close to release quality.
>> Please give them a try and let me know.
>
>It would be nice if we could get rid of cygwin_non_cygwin_dll_entry AT 12
>by next release! However, that will mean breaking binary compat, so 
>may not be an option. Failing that, it really needs to be looked at
>to make sure we're doing everything needed there right now (ie., init'
>ing all the stuff that's needed for a Cygwin DLL loaded by non-cygwin
>app/DLL).
>
>Also, some test runs with gcc-2.95 pre-release snapshots will be quite
>useful. 
>
>Oh, and if we are breaking binary compat, then we should take the 
>opportunity to switch over to using vtable thunks.  
>
>I'm not sure if/when I'll time to do either, so any takers?