From: Al Viro <viro@ftp.linux.org.uk>
To: Derek M Jones <derek@knosof.co.uk>
Cc: Alexey Dobriyan <adobriyan@sw.ru>,
Josh Triplett <josht@linux.vnet.ibm.com>,
linux-sparse@vger.kernel.org, adobriyan@gmail.com
Subject: Re: declaration specifiers wooziness
Date: Wed, 27 Jun 2007 17:00:50 +0100 [thread overview]
Message-ID: <20070627160050.GY21478@ftp.linux.org.uk> (raw)
In-Reply-To: <468285D1.1020506@knosof.co.uk>
On Wed, Jun 27, 2007 at 04:44:17PM +0100, Derek M Jones wrote:
> The point I did not mention before sending the email
> was the extent to which Sparse needs to check constructs
> that are constraint violations and thus assumed to be checked
> by the compiler.
>
> Ok, it is possible to get weird looking stuff through sparse
> without complaint, but is it worth spending time flagging it?
Yes, if they turn into problems later on. One practical reason
is that we are short on MOD_... bits; carrying MOD_LONG et.al.
might be a bad idea - we might want to choose the right integer
type (as in, the right struct symbol out of small set) and be
done with those; conversions can be done that way just fine, we
don't need to look at MOD_LONG et.al. for those.
next prev parent reply other threads:[~2007-06-27 16:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 10:33 declaration specifiers wooziness Alexey Dobriyan
2007-06-27 15:01 ` Josh Triplett
2007-06-27 15:16 ` Derek M Jones
2007-06-27 15:31 ` Alexey Dobriyan
2007-06-27 15:34 ` Derek M Jones
2007-06-27 15:44 ` Derek M Jones
2007-06-27 15:48 ` Josh Triplett
2007-06-27 16:00 ` Al Viro [this message]
2007-06-27 15:39 ` Al Viro
2007-06-27 15:39 ` Josh Triplett
2007-06-27 15:41 ` Al Viro
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=20070627160050.GY21478@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=adobriyan@gmail.com \
--cc=adobriyan@sw.ru \
--cc=derek@knosof.co.uk \
--cc=josht@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.