From: Christopher Li <sparse@chrisli.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Yura Pakhuchiy <pakhuchiy@gmail.com>,
Josh Triplett <josh@freedesktop.org>,
linux-sparse@vger.kernel.org
Subject: Re: [PATCH][RFC] Re: sparse handles int64_t type wrong
Date: Wed, 13 Dec 2006 20:21:04 -0800 [thread overview]
Message-ID: <20061214042104.GB20494@chrisli.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0612131657300.5718@woody.osdl.org>
Never mind my previous patch. It is too simple and wrong.
It can't really tell the C type is abstract or not because
int_ctype has base_type to int_type as well. It ends up applying
the modifiers to int_ctype.
You are right about it is very nasty to delay the finalization
of the C type. Back to drawing board.
Chris
On Wed, Dec 13, 2006 at 04:57:59PM -0800, Linus Torvalds wrote:
>
>
> On Wed, 13 Dec 2006, Christopher Li wrote:
> >
> > Do you mean some thing like this? I might leave some abstract ctype
> > in the tree, it is hard to find all all the user of ctype before
> > it get finalized. It seems work with the test case in my hand.
>
> Yes, this is I think the proper way to do it.
>
> Linus
prev parent reply other threads:[~2006-12-14 4:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 19:34 sparse handles int64_t type wrong Yura Pakhuchiy
2006-12-12 19:44 ` Linus Torvalds
2006-12-12 19:50 ` Yura Pakhuchiy
2006-12-12 20:02 ` Linus Torvalds
2006-12-12 20:25 ` Yura Pakhuchiy
2006-12-13 5:18 ` [PATCH][RFC] " Christopher Li
2006-12-13 15:36 ` Linus Torvalds
2006-12-14 0:13 ` Christopher Li
2006-12-14 0:57 ` Linus Torvalds
2006-12-14 4:21 ` Christopher Li [this message]
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=20061214042104.GB20494@chrisli.org \
--to=sparse@chrisli.org \
--cc=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.org \
--cc=pakhuchiy@gmail.com \
--cc=torvalds@osdl.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.