From: Josh Triplett <josh@joshtriplett.org>
To: Kamil Dudka <kdudka@redhat.com>
Cc: Christopher Li <sparse@chrisli.org>,
Pavel Roskin <proski@gnu.org>,
linux-sparse@vger.kernel.org
Subject: Re: Sparse crash when mixing int and enum in ternary operator
Date: Sat, 27 Mar 2010 02:29:50 -0700 [thread overview]
Message-ID: <20100327092949.GB9548@feather> (raw)
In-Reply-To: <201003271016.39291.kdudka@redhat.com>
On Sat, Mar 27, 2010 at 10:16:38AM +0100, Kamil Dudka wrote:
> On Wednesday 24 of March 2010 11:07:04 Christopher Li wrote:
> > That is just too much. Most of the warning is coming from enum or
> > operation. e.g.
> > .type = KW_SPECIFIER | KW_SHORT,
> > lookup_keyword(token->ident, NS_KEYWORD | NS_TYPEDEF);
>
> Looking once again, I don't think that's the case. The warnings do not come
> from the "enum or" operation, but they come from passing the integral result
> to enum variable (or arg). Instead of weaking my patch, we may improve the
> code of sparse and add explicit casts back to enum:
>
> .type = (enum keyword) (KW_SPECIFIER | KW_SHORT),
> lookup_keyword(token->ident, (enum namespace) (NS_KEYWORD | NS_TYPEDEF));
That looks wrong. .type doesn't contain a value of type "enum keyword",
it contains the bitwise or of such values, which won't represent a valid
enum value. Thus, .type should have an integral type, not an enum type.
The same goes for the second parameter of lookup_keyword.
> The whole problem can be narrowed down to a simple test-case:
>
> int main()
> {
> enum {
> A = 0x1,
> B = 0x2
> } val = A | B;
This code seems semantically wrong, as described above. val should only
have values 0x1 or 0x2, and you've assigned it 0x3, which doesn't
represent a valid value of its enum type.
> Here is what sparse gives:
> $ ./sparse enum.c
> enum.c:1:10: warning: non-ANSI function declaration of function 'main'
> enum.c:6:15: warning: conversion of
> enum.c:6:15: int to
> enum.c:6:15: int enum <noident>
>
>
> Here is what g++ gives:
> $ g++ enum.c
> enum.c: In function ‘int main()’:
> enum.c:6: error: invalid conversion from ‘int’ to ‘main()::<anonymous enum>’
Yup, both of these warnings seem correct. Don't fix them by casting,
fix them by declaring "val" with an appropriate integral type.
- Josh Triplett
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-03-27 9:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 1:24 Sparse crash when mixing int and enum in ternary operator Pavel Roskin
2010-03-09 5:43 ` Christopher Li
2010-03-09 13:46 ` Kamil Dudka
2010-03-09 18:26 ` Pavel Roskin
2010-03-09 18:35 ` Pavel Roskin
2010-03-09 19:06 ` Kamil Dudka
2010-03-09 19:15 ` Josh Triplett
2010-03-09 20:11 ` Pavel Roskin
2010-03-09 20:29 ` Kamil Dudka
2010-03-09 23:30 ` Kamil Dudka
2010-03-10 1:09 ` Pavel Roskin
2010-03-10 16:05 ` Kamil Dudka
2010-03-10 20:27 ` Pavel Roskin
2010-03-10 20:44 ` Kamil Dudka
2010-03-10 21:03 ` Kamil Dudka
2010-03-10 21:56 ` Christopher Li
2010-03-13 17:22 ` Kamil Dudka
2010-03-21 15:27 ` Kamil Dudka
2010-03-24 10:07 ` Christopher Li
2010-03-24 10:51 ` Kamil Dudka
2010-03-27 9:16 ` Kamil Dudka
2010-03-27 9:29 ` Josh Triplett [this message]
2010-03-27 9:53 ` [PATCH] eliminate insane conversions from int to enum Kamil Dudka
2010-03-29 18:11 ` Christopher Li
2010-03-29 18:05 ` Sparse crash when mixing int and enum in ternary operator Christopher Li
2010-03-29 18:17 ` Kamil Dudka
2010-03-29 18:48 ` Christopher Li
2010-03-29 19:23 ` Kamil Dudka
2010-03-30 5:29 ` Pavel Roskin
2010-03-29 21:26 ` Josh Triplett
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=20100327092949.GB9548@feather \
--to=josh@joshtriplett.org \
--cc=kdudka@redhat.com \
--cc=linux-sparse@vger.kernel.org \
--cc=proski@gnu.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).