Re: building and analysing C structs with Storable

Stefan O'Rear <[email protected]> Sun, 14 Oct 2007 12:53:09 -0700
Newsgroups gmane.comp.lang.haskell.libraries,gmane.comp.lang.haskell.ffi
Message-ID <[email protected]>
--===============1986101954==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="sdtB3X0nJg68CQEu"
Content-Disposition: inline


--sdtB3X0nJg68CQEu
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Oct 14, 2007 at 09:28:45PM +0200, Henning Thielemann wrote:
> Do different C compilers on the same platform actually use different=20
> layouts for structs?

Yes, because there are tradeoffs involved.  On x86, the optimal
alignment for long double is 8 bytes, but a lot of people aren't crazy
about 6 bytes of padding per 10 byte datum, so some compilers default to
4 byte alignment.

> If yes, how can I find out, with which compiler a=20
> library was compiled?

Ask the person who did the compiling.

Stefan

--sdtB3X0nJg68CQEu
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHEnOlFBz7OZ2P+dIRAiNIAJ9VzJrvR7ns9UCPAaIVosTW7Fts+gCfYS8i
2t7tQ6UJGY/QWPkHsMu+JWI=
=V4Qp
-----END PGP SIGNATURE-----

--sdtB3X0nJg68CQEu--

--===============1986101954==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Libraries mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/libraries

--===============1986101954==--