X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <48F0116E.1000603@tdragon.net> Date: Fri, 10 Oct 2008 20:37:34 -0600 From: "John E. / TDM" User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com, MinGW Users List Subject: Virtual inheritance & dllimport in GCC 4 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Hi! On the off chance that you're A) reading this message, B) a GCC on Windows hacker, and C) not aware of GCC PR#36654, I'd like to draw your attention to it. This is an interesting problem that arises in builds of recent GCC versions for Windows (i.e. Cygwin and MinGW). Basically, this bug is an ICE that prevents using an inline constructor or destructor in a class which is declared dllimport and which has virtual inheritance anywhere in its ancestry. This is something that works in previous versions of GCC, and I see it as a regression. You can view the GCC PR at . This bug was first brought to my attention by bug #2003723 in the TDM-GCC bug tracker (). I'm posting this attention getter to the MinGW Users and Cygwin mailing lists in hopes of attracting some new blood, as there has not been any progress made on it since the initial bug report on June 27th. I expect the fix will be a one-liner! Thanks in advance, John E. -- 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/