From: Xi Wang <xi.wang@gmail.com>
To: linux-sparse@vger.kernel.org
Subject: simplify_cast() question
Date: Fri, 08 Jun 2012 07:02:16 -0400 [thread overview]
Message-ID: <4FD1DBB8.9010507@gmail.com> (raw)
Hi,
Consider the code:
unsigned int foo(unsigned long long x)
{
unsigned int tmp = x & 0x1fffffff;
return tmp;
}
sparse emits:
and.64 %r2 <- %arg1, $0x1fffffff
ret.32 %r2
%r2 seems to be interpreted as both 64 and 32 bits. Is this the
intended behavior? This could bring some trouble when we add
->ctype to pseudo..
- xi
reply other threads:[~2012-06-08 11:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4FD1DBB8.9010507@gmail.com \
--to=xi.wang@gmail.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.