From: Richard Pennington <rich@pennware.com>
To: musl@lists.openwall.com
Subject: Re: A little more progress today with clang/LLVM
Date: Sat, 26 May 2012 06:59:44 -0500 [thread overview]
Message-ID: <2149672.JvvDDTv0xm@main.pennware.com> (raw)
In-Reply-To: <20292255.R6gnMuUDLb@main.pennware.com>
On Saturday, May 26, 2012 06:30:15 AM Richard Pennington wrote:
[snip]
> > A couple things I'm _NOT_ happy about in my current system are that
> > the whole alltypes.h gets parsed again and again even (for each header
> > that includes it) even if only a few types are needed each time. One
> > thing I'm considering (but not yet decided on) is dropping it and
> > instead having the build system generate all the headers from
> > templates when musl is built, and put the expanded TYPEDEF templates
> > right in the headers that use them.
One somewhat silly reason that I wouldn't want this: a single ELLCC
build/install supports all the targets. Currently I have a single include
directory with target specific headers in target specific subdirectories, e.g.
include/x86_64/bits/alltypes.h with all the other header files common.
Also, I agree with your previous point that it is nice to go to one place
(alltypes.h) to find the processor specific types. If you make this change, at
least keep alltypes.h for reference. ;-)
-Rich
prev parent reply other threads:[~2012-05-26 11:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 1:47 Richard Pennington
2012-05-22 1:59 ` Rich Felker
2012-05-22 2:35 ` Richard Pennington
2012-05-22 2:53 ` Rich Felker
2012-05-22 3:24 ` Richard Pennington
2012-05-25 18:56 ` Richard Pennington
2012-05-25 23:09 ` Rich Felker
2012-05-26 11:30 ` Richard Pennington
2012-05-26 11:39 ` Richard Pennington
2012-05-26 12:49 ` Szabolcs Nagy
2012-05-26 11:59 ` Richard Pennington [this message]
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=2149672.JvvDDTv0xm@main.pennware.com \
--to=rich@pennware.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).