From: Josh Triplett <josh@kernel.org>
To: Geoff Johnstone <geoffsheep.johnstonefrog@googlemail.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: four sparse patches
Date: Mon, 21 Apr 2008 12:12:30 -0700 [thread overview]
Message-ID: <480CE71E.5050608@kernel.org> (raw)
In-Reply-To: <32e600e90804120357k5923dd47xfcb253bf1c390225@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
Geoff Johnstone wrote:
>> Regarding Wmix-decl-code.diff, I agree that that warning definitely
>> needs an option controlling it. but GCC already has that option and
>> calls it "-Wdeclaration-after-statement", so matching GCC's name
>> seems potentially useful. (However, I can imagine corner cases
>> where it might prove problematic, such as wanting to pass that
>> option to GCC and not Sparse or vice versa.) Also, I agree that the
>> default should depend on the C standard in use, and I see no
>> compatibility reason why the warning should remain for code that
>> explicitly asks for C99. Thus, I haven't applied this version of
>> the patch.
>
> I've attached a revised version of the patch that:
> - Renames the option to -Wdeclaration-after-statement, as per GCC
> (wasn't hitherto aware of that gcc option).
> - Defaults based on chosen C dialect.
> - Adds a few tests. (I'll do a separate patch for tests for the
> incomplete struct patch.)
> - Was made wrt the git trunk at about 11:30 UTC on 12th April.
Looks good; applied and pushed. Thanks!
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2008-04-21 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9356e4460803300752y6c1416bfh680b68fd3c42c19a@mail.gmail.com>
[not found] ` <47F07F78.5030405@kernel.org>
[not found] ` <9356e4460803311222v4b09df5fk76268fb5c7e71971@mail.gmail.com>
2008-03-31 19:36 ` four sparse patches Geoff Johnstone
2008-04-05 10:13 ` Josh Triplett
2008-04-12 10:57 ` Geoff Johnstone
2008-04-21 19:12 ` Josh Triplett [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=480CE71E.5050608@kernel.org \
--to=josh@kernel.org \
--cc=geoffsheep.johnstonefrog@googlemail.com \
--cc=linux-sparse@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).