From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Fri, 16 Mar 2007 22:14:48 -0400
From: Kris Maglione <bsdaemon@comcast.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Summer of Code: Call for mentors and students
Message-ID: <20070317021448.GG33600@kris.home>
References: <20070317012939.GF33600@kris.home>
	<af344c7c242fa603afbb29d20b66aa5b@coraid.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="bFsKbPszpzYNtEU6"
Content-Disposition: inline
In-Reply-To: <af344c7c242fa603afbb29d20b66aa5b@coraid.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
Topicbox-Message-UUID: 271fed14-ead2-11e9-9d60-3106f5b1d025


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

On Fri, Mar 16, 2007 at 09:56:31PM -0400, erik quanstrom wrote:
>interesting.  i hadn't thought of going that way.  i was afraid of non-obv=
ious
>breakage.=20

I'd considered it, but things like __^(extension attribute)^__ shouldn't=20
cause breakage. __alignment__ certainly could, and there are some ugly=20
ones, but the BSD headers are considerably cleaner than the glibc=20
headers, so I didn't have to deal with too much.

>what do you do about inline?  what do do you about asm?  unfortunately a q=
uick
>grep of even the first level of /usr/include on linux  shows some asm goo.

Well, in the BSD headers, at least, there's only one instance of __asm__=20
that appears outside of a macro, and that's in an FSF header that is=20
full of inline functions and all kinds of other such goo. I'll just have=20
to hope that nothing I need to compile includes it ;) The ones in the=20
macros obviously don't matter unless they're used.

--=20
Kris Maglione

If you can get to the faulty part, you don't have the
tool to get it off.

--bFsKbPszpzYNtEU6
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.2 (FreeBSD)

iD8DBQFF+08YseQZD8Aui4wRAjhcAJ9RfbuPhoCsDTh9VogSLIZwkU2RTACfcNfW
2wpBPT6ngZSI7jE6dWrtWEw=
=BJuI
-----END PGP SIGNATURE-----

--bFsKbPszpzYNtEU6--