All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Li <sparse@chrisli.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Pavel Roskin <proski@gnu.org>, linux-sparse@vger.kernel.org
Subject: Re: Feature request - suppress warnings for system libraries
Date: Fri, 2 Feb 2007 15:03:17 -0800	[thread overview]
Message-ID: <20070202230317.GE27667@chrisli.org> (raw)
In-Reply-To: <20070202231705.GF10050@ftp.linux.org.uk>

On Fri, Feb 02, 2007 at 11:17:05PM +0000, Al Viro wrote:
> On Fri, Feb 02, 2007 at 02:31:55PM -0800, Christopher Li wrote:
> 
> I'm not sure.  __transparent_union__ is an atrocious kludge and it does
> deserve a warning.  So getting it to STFU on known offenders we have no
> chance to fix is OK, but legitimizing that abortion is not.

I did not mean to legitimizing it. I just don't want to silence
suppress this kind of warnings.

> Unlike __transparent_union__, restrict is at least a valid C...  It's not
> that hard to handle, except for the shortage of bits for modifiers...

I have a patch free up the specials bits in modifiers. It helps a little
bit. But I think we need a attribute pointer in ctype to fit more attributes
eventually.

Chris

  reply	other threads:[~2007-02-02 23:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-02 17:43 Feature request - suppress warnings for system libraries Pavel Roskin
2007-02-02 22:01 ` Christopher Li
2007-02-02 22:37   ` Pavel Roskin
2007-02-02 22:31     ` Christopher Li
2007-02-02 23:17       ` Al Viro
2007-02-02 23:03         ` Christopher Li [this message]
2007-02-02 23:25         ` Linus Torvalds
2007-02-03  0:30           ` Al Viro
2007-02-03  0:40             ` 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=20070202230317.GE27667@chrisli.org \
    --to=sparse@chrisli.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=proski@gnu.org \
    --cc=viro@ftp.linux.org.uk \
    /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.