From: Kamil Dudka <kdudka@redhat.com>
To: Christopher Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] do not ignore attribute 'noreturn'...
Date: Mon, 14 Sep 2009 19:32:12 +0200 [thread overview]
Message-ID: <200909141932.12684.kdudka@redhat.com> (raw)
In-Reply-To: <70318cbf0909141027y69ddecc2y591ffb6aca300fca@mail.gmail.com>
On Monday 14 of September 2009 19:27:40 Christopher Li wrote:
> 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.
Thanks! It makes sense to me.
As for the long term solution, I don't think it's possible without breaking
the current API/ABI. What about using a bitfield instead? I can see it solved
this way in <gcc/tree.h>.
Kamil
next prev parent reply other threads:[~2009-09-14 17:33 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
2009-09-14 17:32 ` Kamil Dudka [this message]
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=200909141932.12684.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 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.