From: Josh Triplett <josh@freedesktop.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] fix handling of address_space in casts and assignments
Date: Wed, 11 Jul 2007 23:44:05 -0700 [thread overview]
Message-ID: <4695CDB5.5080605@freedesktop.org> (raw)
In-Reply-To: <20070709221306.GP21668@ftp.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
Al Viro wrote:
> Turn FORCE_MOD into storage class specifier (that's how it's
> actually used and that makes for much simpler logics).
>
> Introduce explicit EXPR_FORCE_CAST for forced casts; handle it
> properly.
>
> Kill the idiocy in get_as() (we end up picking the oddest things
> for address space - e.g. if we have int __attribute__((address_space(1))) *p,
> we'll get warnings about removal of address space when we do things like
> (unsigned short)*p. Fixed. BTW, that had caught a bunch of very odd
> bogosities in the kernel and eliminated several false positives in there.
>
> As the result, get_as() is gone now and evaluate_cast() got simpler.
>
> Kill the similar idiocy in handling pointer assignments; while we are at it,
> fix the qualifiers check for assignments to/from void * (you can't assign
> const int * to void * - qualifiers on the left side should be no less than
> on the right one; for normal codepath we get that checked, but the special
> case of void * skips these checks).
Applied (yesterday); thanks!
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2007-07-12 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 22:13 [PATCH] fix handling of address_space in casts and assignments Al Viro
2007-07-10 1:07 ` [PATCH] fix handling of pointers in ?: Al Viro
2007-07-12 6:44 ` Josh Triplett
2007-07-12 6:44 ` 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=4695CDB5.5080605@freedesktop.org \
--to=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.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.