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: Sat, 05 Apr 2008 03:13:30 -0700 [thread overview]
Message-ID: <47F750CA.1090307@kernel.org> (raw)
In-Reply-To: <32e600e90803311236g4caf05c9t8dd3a3ab03dcd5bc@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]
Geoff Johnstone wrote:
>>> I've attached four patches that I've written for sparse to
>>> use it for a userland project.
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'd love to apply
an updated version with those two changes.
Regarding incomplete structs, your patch seems reasonable as far as I
know, and it doesn't break the test suite, so I've applied and pushed
it. Per your concerns, if this patch doesn't represent the correct
fix, the code can change later when we have a test case that breaks
with this patch. Please do consider writing a patch for a new test
case based on your example.
Your argument parsing for -ansi and -std= looks great to me. Applied
and pushed.
The new builtins for fortify handling seem fine. Applied and pushed.
Thanks for your patches.
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2008-04-05 10:13 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 [this message]
2008-04-12 10:57 ` Geoff Johnstone
2008-04-21 19:12 ` Josh Triplett
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=47F750CA.1090307@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).