From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@transmeta.com>, rth@twiddle.net
Subject: required C optimizations?
Date: Mon, 02 Sep 2002 15:25:13 -0400 [thread overview]
Message-ID: <3D73BB19.6000302@mandrakesoft.com> (raw)
Hi all,
I'm trying to get an idea of the minimum compiler requirements necessary
to build a Linux kernel, excluding parsing requirements. For example,
IIRC, some portions of the code depend on 'static inline' working and
decent constant propagation/folding.
Are you guys aware of a list of such examples, either in your own head
or written down somewhere?
If you're wondering what this is about, I'm playing around with "tinycc"
(http://www.tinycc.org/) ... it's nowhere near building a kernel, being
basically a C parser that emits binary code, but I wanted to get an idea
of the obstacles.
Jeff
reply other threads:[~2002-09-02 19:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3D73BB19.6000302@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
--cc=torvalds@transmeta.com \
/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