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
Date: Fri, 16 Mar 2007 22:14:48 -0400 [thread overview]
Message-ID: <20070317021448.GG33600@kris.home> (raw)
In-Reply-To: <af344c7c242fa603afbb29d20b66aa5b@coraid.com>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
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-obvious
>breakage.
I'd considered it, but things like __^(extension attribute)^__ shouldn't
cause breakage. __alignment__ certainly could, and there are some ugly
ones, but the BSD headers are considerably cleaner than the glibc
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 quick
>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__
that appears outside of a macro, and that's in an FSF header that is
full of inline functions and all kinds of other such goo. I'll just have
to hope that nothing I need to compile includes it ;) The ones in the
macros obviously don't matter unless they're used.
--
Kris Maglione
If you can get to the faulty part, you don't have the
tool to get it off.
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2007-03-17 2:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 18:08 Kris Maglione
2007-03-15 18:40 ` Skip Tavakkolian
2007-03-15 18:47 ` Devon H. O'Dell
2007-03-15 19:16 ` Kris Maglione
2007-03-15 19:30 ` andrey mirtchovski
2007-03-15 19:43 ` Kris Maglione
2007-03-15 22:39 ` andrey mirtchovski
2007-03-15 22:40 ` andrey mirtchovski
2007-03-17 0:50 ` Fernan Bolando
2007-03-17 1:11 ` Kris Maglione
2007-03-17 1:12 ` erik quanstrom
2007-03-17 1:29 ` Kris Maglione
2007-03-17 1:56 ` erik quanstrom
2007-03-17 2:14 ` Kris Maglione [this message]
2007-03-15 19:47 ` Skip Tavakkolian
2007-03-15 19:49 ` Kris Maglione
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070317021448.GG33600@kris.home \
--to=bsdaemon@comcast.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).