From: Kamil Dudka <kdudka@redhat.com>
To: Christopher Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: enum warning patch (was Re: Defect in linearization of short circuit &&)
Date: Wed, 17 Feb 2010 15:00:26 +0100 [thread overview]
Message-ID: <201002171500.27119.kdudka@redhat.com> (raw)
In-Reply-To: <70318cbf1002161444m6daa6a9dh7f30d347b4e9ebbb@mail.gmail.com>
On Tue February 16 2010 23:44:08 Christopher Li wrote:
> Most simple enum declare has very small set of values. So naturally I
> might want to use
> some thing smaller than int type to store the enum value. I can't find
> a good way to play
> well with the enum warnings.
>
> If I use "char type" to store it. It trigger warning when you assign to it.
> If I use "enum foo_type type:8" to store it, it will use int type
> alignment and padding which
> defeat the purpose of using a smaller type.
>
> Any suggestion?
I don't think it's that easy to implement while keeping it enough generic.
You need either a type able to store _any_ enum value, or a kind of type
with variable size to keep it still working. The second seems like quite
a lot of fuss over 4 bytes of memory.
Kamil
next prev parent reply other threads:[~2010-02-17 14:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-14 13:39 Defect in linearization of short circuit && Jacek Śliwerski
2010-02-14 21:04 ` Jacek Śliwerski
2010-02-14 23:09 ` Christopher Li
2010-02-15 19:12 ` Jacek Śliwerski
2010-02-15 19:41 ` Christopher Li
2010-02-15 20:18 ` Jacek Śliwerski
2010-02-15 21:11 ` Christopher Li
2010-02-16 9:28 ` Bernd Petrovitsch
2010-02-16 19:02 ` Christopher Li
2010-02-16 19:10 ` Christopher Li
2010-02-16 19:19 ` Jacek Śliwerski
2010-02-16 19:36 ` Christopher Li
2010-02-16 20:11 ` enum warning patch (was Re: Defect in linearization of short circuit &&) Kamil Dudka
2010-02-16 20:18 ` Kamil Dudka
2010-02-16 22:44 ` Christopher Li
2010-02-17 14:00 ` Kamil Dudka [this message]
2010-02-17 11:47 ` Defect in linearization of short circuit && Bernd Petrovitsch
2010-02-17 20:22 ` Christopher Li
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=201002171500.27119.kdudka@redhat.com \
--to=kdudka@redhat.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).