From: Christopher Li <sparse@chrisli.org>
To: Kamil Dudka <kdudka@redhat.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] do not ignore attribute 'noreturn'...
Date: Mon, 14 Sep 2009 10:27:40 -0700 [thread overview]
Message-ID: <70318cbf0909141027y69ddecc2y591ffb6aca300fca@mail.gmail.com> (raw)
In-Reply-To: <70318cbf0908281444q735b7b9fm73f0fcbdbaeefa7b@mail.gmail.com>
On Fri, Aug 28, 2009 at 2:44 PM, Christopher Li <sparse@chrisli.org> wrote:
> Yes, no return is kind of useful. I think we need to do some thing about the
> MOD_XXX eventually. It is very easy to run out of bits there.
>
Ah, the MOD_NORETURN is bigger than size of long in 32 bit systems.
I just get a few warning from GCC.
I just relocate the MOD_NORETURN bits.
Chris
diff --git a/symbol.h b/symbol.h
index 80ef363..9f5a32f 100644
--- a/symbol.h
+++ b/symbol.h
@@ -214,10 +214,10 @@ struct symbol {
#define MOD_SAFE 0x8000000 // non-null/non-trapping pointer
#define MOD_USERTYPE 0x10000000
+#define MOD_NORETURN 0x20000000
#define MOD_EXPLICITLY_SIGNED 0x40000000
#define MOD_BITWISE 0x80000000
-#define MOD_NORETURN 0x100000000
#define MOD_NONLOCAL (MOD_EXTERN | MOD_TOPLEVEL)
#define MOD_STORAGE (MOD_AUTO | MOD_REGISTER | MOD_STATIC | MOD_EXTERN | MOD
next prev parent reply other threads:[~2009-09-14 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 21:30 [PATCH] do not ignore attribute 'noreturn' Kamil Dudka
2009-08-28 21:44 ` Christopher Li
2009-09-14 17:27 ` Christopher Li [this message]
2009-09-14 17:32 ` Kamil Dudka
2009-09-14 17:55 ` Christopher Li
2009-09-14 19:44 ` Kamil Dudka
2009-09-14 20:47 ` Christopher Li
2009-09-14 21:13 ` Kamil Dudka
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=70318cbf0909141027y69ddecc2y591ffb6aca300fca@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=kdudka@redhat.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 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).