mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: A little more progress today with clang/LLVM
Date: Mon, 21 May 2012 21:59:35 -0400	[thread overview]
Message-ID: <20120522015935.GQ163@brightrain.aerifal.cx> (raw)
In-Reply-To: <6099278.PLLg0Rc9Yf@main.pennware.com>

On Mon, May 21, 2012 at 08:47:04PM -0500, Richard Pennington wrote:
> I've decided to keep the musl build scheme with a few minor changes (e.g. 
> replace libgcc.a with libcompiler-rt.a).
> 
> I'm now building for i386, arm, and x86_64. I enabled clang warnings -Werror 
> and had to inhibit a few, some of which look like they need some attention. 
> Here's my current list:
> 
> -Werror -Qunused-arguments -Wno-unneeded-internal-declaration -Wno-cast-align 
> -Wno-incompatible-pointer-types -Wno-implicit-function-declaration -Wno-
> string-plus-int -Wno-pointer-sign -Wno-array-bounds

Aside from unused arguments (a bogus warning IMO) and string plus int
(why is this a warning?), these sound like they could be issues to
address. I cleaned up all the pointer signedness warnings (which
should be errors, per the C language) with gcc, so I'm unsure why
they're showing up again. Implicit function declarations sound
particularly bad, but gcc didn't report any to me. The rest are
*probably* non-issues, but I'd like to check them if you could send
the warning output to the list.

> I think that bits/alltypes.h might need some clang specific tweaking.

Can you elaborate?

> I'm going to start looking at the mips, ppc, and microblaze bits now, and will 
> look at warning elimination after.

I'll be happy to look at it for you. :)

Rich


  reply	other threads:[~2012-05-22  1: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 [this message]
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

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=20120522015935.GQ163@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --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).