From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Lance Richardson <lrichard@redhat.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH v2] sparse: add support for static assert
Date: Fri, 29 Jan 2016 17:15:56 +0100 [thread overview]
Message-ID: <20160129161554.GA730@macbook.lan> (raw)
In-Reply-To: <67630678.27333596.1453992809485.JavaMail.zimbra@redhat.com>
On Thu, Jan 28, 2016 at 09:53:29AM -0500, Lance Richardson wrote:
> ----- Original Message -----
> > On Mon, Jan 11, 2016 at 05:31:22PM -0500, Lance Richardson wrote:
> >
> >
> > Hi,
> >
> > I don't understand why tha parsing part have changed so much since v1.
>
> I discovered as I was adding additional test cases that the NS_TYPEDEF
> approach was causing sizeof to report a zero size for structures with
> embedded _Static_assert(); as part of processing NS_TYPEDEF within
> a structure for _Static_assert(), a unnamed field with unknown size
> was being attached to the structure definition.
>
> So I decided to take a different approach, one that hopefully makes
> more sense than handling _Static_assert() via NS_TYPEDEF.
>
> Apologies for not providing these details in the v2 commit log.
OK, I understand.
Yes, it's certainly worth to add that in the patch description.
> > > +struct s2 {
> > > + char c;
> > > + _Static_assert(sizeof(struct s2) == 1, "struct sizeof");
> > > +};
> >
> > This succeed but
> > struct s2 {
> > char c;
> > _Static_assert(sizeof(struct s2) == 1, "struct sizeof");
> > char d;
> > _Static_assert(sizeof(struct s2) == 2, "struct sizeof");
> > };
> > succeed also wich seems certainly very odd.
> >
>
> Yes, I believe they should both fail with something like "invalid use of
> sizeof on incomplete type".
>
> I think it's a bug.
>
Absolutely.
>
> OK, I'll post a v3 with the invalid test case removed. Thanks for looking
> at this.
>
> Lance
Good.
Please also add the explanation about the parsing in the patch description.
Luc
prev parent reply other threads:[~2016-01-29 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 22:31 [PATCH v2] sparse: add support for static assert Lance Richardson
2016-01-25 18:48 ` Luc Van Oostenryck
2016-01-28 14:53 ` Lance Richardson
2016-01-29 16:15 ` Luc Van Oostenryck [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=20160129161554.GA730@macbook.lan \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=lrichard@redhat.com \
/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.