mailing list of musl libc
 help / color / mirror / code / Atom feed
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:30:15 -0500	[thread overview]
Message-ID: <20292255.R6gnMuUDLb@main.pennware.com> (raw)
In-Reply-To: <20120525230938.GZ163@brightrain.aerifal.cx>

On Friday, May 25, 2012 07:09:38 PM Rich Felker wrote:
> On Fri, May 25, 2012 at 01:56:56PM -0500, Richard Pennington wrote:
> > I've done a little hacking on alltypes.h.sh which I'm in the process of
> > 
> > testing. I have two goals:
> > 	1. Make it work with clang's headers.
> 
> Can you explain what the issue is? Are you talking about issues
> building clang itself, or building programs against musl using clang?
> In the latter case, musl does not use or support using
> compiler-provided headers. All of the standard headers are provided
> fully by musl.

This is good to know. I'll stop using the compiler supplied headers.

[snip]
> One thing that _would_ work for these __typeof__ cases is to put it
> under __GNUC__, which encompasses ALL compilers that have "GNU C"
> extensions like typeof. That would definitely be an acceptable change,
> but unless there are any compilers where it's necessary, I'd rather
> just leave the types explicit for the arch's ABI. One of the most
> frustrating things with glibc headers is never being able to figure
> out the actual underlying definition of a type, and I'd like not to
> recreate that frustration.

You've convinced me. ;-)

> 
> 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.
> 
> In any case, for now don't worry about the potential
> ugliness/duplication in alltypes.h.sh for new archs. It's not a large
> file (the bits/*.h headers are much worse when it comes to
> duplication) and I'm happy to take responsibility for cleaning them
> all up later if a better system is devised.
> 

OK, and thanks for being patient. I'm still trying to absorb the musl 
philosophy.

-Rich


  reply	other threads:[~2012-05-26 11:30 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 [this message]
2012-05-26 11:39         ` Richard Pennington
2012-05-26 12:49           ` Szabolcs Nagy
2012-05-26 11:59         ` Richard Pennington

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=20292255.R6gnMuUDLb@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).