From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Theodore Ts'o" <tytso@mit.edu>,
linux-ext4@vger.kernel.org, Zheng Liu <wenqing.lz@taobao.com>,
Christopher Li <sparse@chrisli.org>,
linux-sparse@vger.kernel.org
Subject: Re: [PATCH 03/10 v3] ext4: add physical block and status member into extent status tree
Date: Sun, 3 Feb 2013 11:19:43 +0300 [thread overview]
Message-ID: <20130203081943.GF4937@mwanda> (raw)
In-Reply-To: <20130203052113.GA9823@gmail.com>
On Sun, Feb 03, 2013 at 01:21:13PM +0800, Zheng Liu wrote:
> On Sat, Feb 02, 2013 at 10:03:43PM -0500, Theodore Ts'o wrote:
> > On Wed, Jan 30, 2013 at 10:43:33AM +0800, Zheng Liu wrote:
> > >
> > > Clang is first coming in my mind. I know that some one try to use it
> > > to build a linux kernel and get a lot of problems that are about gcc
> > > extension. But for us it seems that things are not too bad. ;)
> >
> > Clang accepts bitfields with "unsigned long long", but I've discovered
> > something which does _not_ support unsigned long long --- the "sparse"
> > tool. :-(
>
> Yes, this problem has been reported by Fengguang. So I am plan to use
> another method to define extent_status structure as last time we
> discuessed. What do you think?
>
I don't get this warning on my version of Sparse.
Sparse used to assume -m32 all the time but now that's been changed.
Are you using the most recent version of Sparse? Try passing -m64.
regards,
dan carpenter
next prev parent reply other threads:[~2013-02-03 8:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 12:03 [PATCH 00/10 v3] ext4: extent status tree (step2) Zheng Liu
2013-01-23 12:03 ` [PATCH 01/10 v3] ext4: refine extent status tree Zheng Liu
2013-01-23 12:03 ` [PATCH 02/10 v3] ext4: remove EXT4_MAP_FROM_CLUSTER flag Zheng Liu
2013-01-23 12:03 ` [PATCH 03/10 v3] ext4: add physical block and status member into extent status tree Zheng Liu
2013-01-29 3:03 ` Theodore Ts'o
2013-01-29 5:34 ` Zheng Liu
2013-01-29 17:28 ` Theodore Ts'o
2013-01-30 2:43 ` Zheng Liu
2013-02-03 3:03 ` Theodore Ts'o
2013-02-03 5:21 ` Zheng Liu
2013-02-03 8:19 ` Dan Carpenter [this message]
2013-02-03 14:57 ` Theodore Ts'o
2013-02-03 7:30 ` Sam Ravnborg
2013-01-23 12:03 ` [PATCH 04/10 v3] ext4: adjust interfaces of " Zheng Liu
2013-01-23 12:03 ` [PATCH 05/10 v3] ext4: track all extent status in " Zheng Liu
2013-01-23 12:03 ` [PATCH 06/10 v3] ext4: lookup block mapping " Zheng Liu
2013-01-23 12:03 ` [PATCH 07/10 v3] ext4: remove single extent cache Zheng Liu
2013-01-23 12:03 ` [PATCH 08/10 v3] fs: allow for fs-specific objects to be pruned as part of pruning inodes Zheng Liu
2013-01-23 12:03 ` [PATCH 09/10 v3] ext4: adjust some functions for reclaiming extents from extent status tree Zheng Liu
2013-01-23 12:04 ` [PATCH 10/10 v3] ext4: reclaim " Zheng Liu
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=20130203081943.GF4937@mwanda \
--to=dan.carpenter@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
--cc=tytso@mit.edu \
--cc=wenqing.lz@taobao.com \
/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.