Date: Fri, 7 Nov 2008 03:39:25 GMT From: Peter Wemm <peter@FreeBSD.org> To: Perforce Change Reviews <perforce@freebsd.org> Subject: PERFORCE change 152609 for review Message-ID: <200811070339.mA73dP9Z074050@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
http://perforce.freebsd.org/chv.cgi?CH=152609 Change 152609 by peter@peter_hammer on 2008/11/07 03:38:43 Shuffle typedefs to be after definitions. gcc3 cares about this. Affected files ... .. //depot/projects/valgrind/coregrind/pub_core_initimg.h#3 edit Differences ... ==== //depot/projects/valgrind/coregrind/pub_core_initimg.h#3 (text+ko) ==== @@ -40,26 +40,6 @@ // the AIX kernel does most of the work for us. //-------------------------------------------------------------------- -/* These are OS-specific and defined below. */ -typedef struct _IICreateImageInfo IICreateImageInfo; -typedef struct _IIFinaliseImageInfo IIFinaliseImageInfo; - -/* This is a two stage process. The first stage, which is most of the - work, creates the initial image in memory to the extent possible. - To do this it takes a bundle of information in an IICreateImageInfo - structure, which is gathered in an OS-specific way at startup. - This returns an IIFinaliseImageInfo structure: */ -extern -IIFinaliseImageInfo VG_(ii_create_image)( IICreateImageInfo ); - -/* Just before starting the client, we may need to make final - adjustments to its initial image. Also we need to set up the VEX - guest state for thread 1 (the root thread) and copy in essential - starting values. This is handed the IIFinaliseImageInfo created by - VG_(ii_create_image). */ -extern -void VG_(ii_finalise_image)( IIFinaliseImageInfo ); - /* Note that both IICreateImageInfo and IIFinaliseImageInfo are OS-specific. We now go on to give instantiations of them @@ -174,6 +154,25 @@ #endif +typedef struct _IICreateImageInfo IICreateImageInfo; +typedef struct _IIFinaliseImageInfo IIFinaliseImageInfo; + +/* This is a two stage process. The first stage, which is most of the + work, creates the initial image in memory to the extent possible. + To do this it takes a bundle of information in an IICreateImageInfo + structure, which is gathered in an OS-specific way at startup. + This returns an IIFinaliseImageInfo structure: */ +extern +IIFinaliseImageInfo VG_(ii_create_image)( IICreateImageInfo ); + +/* Just before starting the client, we may need to make final + adjustments to its initial image. Also we need to set up the VEX + guest state for thread 1 (the root thread) and copy in essential + starting values. This is handed the IIFinaliseImageInfo created by + VG_(ii_create_image). */ +extern +void VG_(ii_finalise_image)( IIFinaliseImageInfo ); + #endif // __PUB_CORE_INITIMG_H /*--------------------------------------------------------------------*/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200811070339.mA73dP9Z074050>