Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Mon, 9 Jun 2003 10:02:34 +0200 From: Rasmus Hahn To: cygwin AT cygwin DOT com Subject: Re: Problem w/ c++,threads,static initializers Message-ID: <20030609100234.A19101@hamburg.neofonie.local> References: <20030607142449 DOT A4909 AT hamburg DOT neofonie DOT local> <3EE2256B DOT 7060908 AT cygwin DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3EE2256B.7060908@cygwin.com>; from cygwin-lh@cygwin.com on Sat, Jun 07, 2003 at 01:48:27PM -0400 However, the cygwin-gcc is not a 3.3 and is has some bugs. Since the cygwin dll source is in large parts c++ i thought some bugs of the `wrong-code'-kind could creep into cygwin1.dll. Since i do not know the innards of cygwin very well i recompiled the dll just to be sure, but i dont really know if this is necessary. I send a small code example that fails with the gcc-3.2 that demonstrates a problematic construct. This is a known gcc-problem and doesnt strictly belong here, but perhaps someone reading it would be able to say if this is relevant to the cygwin-dll. Likely that all this has nothing to do with the original message. Greetings - Rasmus // bug-code: gcc-3.2 wont call destructor of D #include struct D { D () { printf ("D ()\n"); } ~D () { printf ("~D (this=%p)\n", this); } }; void use_D (D d) { } const D make_D () { return D (); } int main () { use_D (make_D ()); } // end of code On Sat, Jun 07, 2003 at 01:48:27PM -0400, Larry Hall wrote: > Rasmus Hahn wrote: > > > BTW i am using cygwin snapshot 20030602 compiled with gcc-3.3 since the > > out-of-the-box gcc from the cygwin-package is a prerelease and definitely > > contains bugs that do not allow it to compile my code. > > > As previously mentioned on this list, the gcc that comes with Cygwin is > version 3.2. It is *not* a prerelease of gcc 3.2, despite the "comment" > in 'gcc -version'. Obviously, I can't speak to the applicability of > gcc 3.2 to your code or the problems you have compiling with it but I > wanted to dispel any notion that Cygwin's gcc is somehow an early version > of the official gcc 3.2 release. > > > -- > Larry Hall http://www.rfk.com > RFK Partners, Inc. (508) 893-9779 - RFK Office > 838 Washington Street (508) 893-9889 - FAX > Holliston, MA 01746 > > > ################################################################# > ################################################################# > ################################################################# > ##### > ##### > ##### > ################################################################# > ################################################################# > ################################################################# -- -- 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/