From: Christopher Li <sparse@chrisli.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH] Fix type_info_expression()
Date: Thu, 5 Feb 2009 12:21:24 -0800 [thread overview]
Message-ID: <70318cbf0902051221y7ec61944m3880bf52fbbbbb1a@mail.gmail.com> (raw)
In-Reply-To: <20090205192322.GN28946@ZenIV.linux.org.uk>
On Thu, Feb 5, 2009 at 11:23 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> On Thu, Feb 05, 2009 at 10:29:19AM -0800, Christopher Li wrote:
> Take a look at evaluate_type_information(). If ->cast_type is not NULL,
> it won't even look at ->cast_expression. For sizeof (struct foo){0,1} that's
> fine (you end with with sizeof(struct foo), essentially), but for
> sizeof(struct foo){0,1}.x that'll give you the wrong answer.
>
> IOW, it is necessary.
That is the subtle detail I am looking for.
I will apply your patch.
Thanks
Chris
prev parent reply other threads:[~2009-02-05 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 7:31 [PATCH] Fix type_info_expression() Al Viro
2009-02-05 18:29 ` Christopher Li
2009-02-05 19:23 ` Al Viro
2009-02-05 20: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=70318cbf0902051221y7ec61944m3880bf52fbbbbb1a@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).