From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Lpl2K-0000Pc-2o
	for qemu-devel@nongnu.org; Fri, 03 Apr 2009 11:10:28 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Lpl2E-0000PP-Nm
	for qemu-devel@nongnu.org; Fri, 03 Apr 2009 11:10:26 -0400
Received: from [199.232.76.173] (port=51630 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Lpl2E-0000PM-I3
	for qemu-devel@nongnu.org; Fri, 03 Apr 2009 11:10:22 -0400
Received: from mx20.gnu.org ([199.232.41.8]:59330)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <paul@codesourcery.com>)
	id 1Lpl2E-000426-BB
	for qemu-devel@nongnu.org; Fri, 03 Apr 2009 11:10:22 -0400
Received: from mail.codesourcery.com ([65.74.133.4])
	by mx20.gnu.org with esmtp (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1Lpl2D-0002Jo-5x
	for qemu-devel@nongnu.org; Fri, 03 Apr 2009 11:10:21 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [RFC] Introduce module API to QEMU
Date: Fri, 3 Apr 2009 15:10:16 +0000
References: <1238724755-15929-1-git-send-email-aliguori@us.ibm.com>
	<20090403140419.GA23421@caradoc.them.org>
	<49D62338.30009@redhat.com>
In-Reply-To: <49D62338.30009@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200904031610.17471.paul@codesourcery.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@us.ibm.com>, Avi Kivity <avi@redhat.com>

> > Yes, this does raise the question of how __attribute__((constructor))
> > works.  Maybe it's specific to new named sections?  Maybe I'm just
> > misremembering.  Anyway, whatever you come up with, testing on
> > Windows would be a good idea if you haven't already.
>
> I'm guessing it's just a C interface to C++ static constructors.  Since
> gcc supports C++ on Windows, I'd expect this to work.

It it has to, gcc will resort to using the equivalent of nm | grep on your 
object files to generate a list of constructors.

Paul