From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH] git-compat-util.h: Don't define NORETURN under __clang__
Date: Tue, 3 Aug 2010 21:10:34 +0000 [thread overview]
Message-ID: <AANLkTinNkLNGjFrfmo5za_D10AkcMEMzA8yppA+H+YMe@mail.gmail.com> (raw)
In-Reply-To: <vpqvd7rzsfa.fsf@bauges.imag.fr>
Thanks everyone. I should have tested a later version of clang before
I sent the patch. It might still be worthwhile to munge the flags for
old clangs so that git doesn't error out on it, but if 1.0 doesn't
make it into some major OS release and gcc remains the default it's
not much of an issue.
On Tue, Aug 3, 2010 at 14:23, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> wrote:
> Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
>
>> (other than that, it's cool to see someone testing another
>> compiler ;-) )
>
> BTW, the only warnings remaining with -Wall with my clang are:
>
> imap-send.c:548:27: warning: data argument not used by format string [-Wformat-extra-args]
> cmd->tag, cmd->cmd, cmd->cb.dlen);
> ^
I didn't look into that one. It'd be usefu to check out if the format
string is really incomplete there, or if clang is just failing it its
analysis.
That's some hairy code, in any case.
> imap-send.c:1089:41: warning: conversion specifies type 'unsigned short' but the argument has type 'int' [-Wformat]
> snprintf(portstr, sizeof(portstr), "%hu", srvc->port);
> ~~^ ~~~~~~~~~~
> 2 diagnostics generated.
Looks like that needs a cast.
next prev parent reply other threads:[~2010-08-03 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 13:08 [RFC/PATCH] git-compat-util.h: Don't define NORETURN under __clang__ Ævar Arnfjörð Bjarmason
2010-08-03 13:18 ` Michael J Gruber
2010-08-03 13:35 ` Matthieu Moy
2010-08-03 14:23 ` Matthieu Moy
2010-08-03 21:10 ` Ævar Arnfjörð Bjarmason [this message]
2010-08-03 13:35 ` Benjamin Kramer
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=AANLkTinNkLNGjFrfmo5za_D10AkcMEMzA8yppA+H+YMe@mail.gmail.com \
--to=avarab@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
/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).