From: Rick Hohensee <humbubba@smarty.smart.net>
To: 9fans@cse.psu.edu
Subject: [9fans] partial-Plan9ification question
Date: Thu, 12 Jul 2001 18:16:00 -0400 [thread overview]
Message-ID: <200107122216.SAA29875@smarty.smart.net> (raw)
Hi.
Given a POSIXy unix, with lots of inline assembly interlaced in the C
with Gcc asm(""), consider losing all the asm("") in lieu of C-called
assembly and inlined C. This presents a factoring problem for header files
and so on relative to unix. Given also that Plan 9's header structure is
the best for languages like C, and given that we want that Plan9ism, but
not the cross-compile facilities any time soon, how would you restructure
the sources? (I'll be presuming my whole world is one cpu.) I know I'll
need a cpu.S, a cpu.o, but then things get variable. I'll also probably be
doing ld-related #pragmas, and maybe a mk or a proto-mk in sh, but I don't
know that that pertains to the above issue if I just assume one CPU. Care
to comment, maestros?
Rick Hohensee
www.clienux.com
next reply other threads:[~2001-07-12 22:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-12 22:16 Rick Hohensee [this message]
2001-07-12 22:18 ` Boyd Roberts
2001-07-13 1:55 ` Rick Hohensee
-- strict thread matches above, loose matches on Subject: below --
2001-07-13 22:34 David Gordon Hogan
2001-07-13 19:15 David Gordon Hogan
2001-07-13 18:08 brucee
2001-07-13 18:37 ` Rick Hohensee
2001-07-13 6:39 David Gordon Hogan
2001-07-13 6:23 David Gordon Hogan
2001-07-13 18:26 ` Rick Hohensee
2001-07-13 5:53 forsyth
2001-07-13 6:26 ` Mike Haertel
2001-07-12 22:08 David Gordon Hogan
2001-07-13 1:27 ` Rick Hohensee
2001-07-13 14:53 ` Douglas A. Gwyn
2001-07-13 22:18 ` Dan Cross
2001-07-14 1:21 ` Boyd Roberts
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=200107122216.SAA29875@smarty.smart.net \
--to=humbubba@smarty.smart.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).