linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lance Richardson <lrichard@redhat.com>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH v4] sparse: add support for _Static_assert
Date: Thu, 4 May 2017 11:46:55 -0400 (EDT)	[thread overview]
Message-ID: <99956653.4916117.1493912815498.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170504145834.mef3psritw2lxf35@ltop.local>

> From: "Luc Van Oostenryck" <luc.vanoostenryck@gmail.com>
> To: "Lance Richardson" <lrichard@redhat.com>
> Cc: "Linux-Sparse" <linux-sparse@vger.kernel.org>
> Sent: Thursday, 4 May, 2017 10:58:35 AM
> Subject: Re: [PATCH v4] sparse: add support for _Static_assert
> 
> On Thu, May 04, 2017 at 09:53:50AM -0400, Lance Richardson wrote:
> > Thanks for the quick feedback, will incorporate in v5.
> 
> I also saw a small issue, possibly related to the problem with
> the mixup between 'declaration-list' and 'struct-declarator-list'
> that you noticed. In the following code, the static assert is not
> recognized:
> 	void foo(void)
> 	{
> 		int i = 0;
> 		for (_Static_assert(1, "ok"); 1; )
> 			;
> 		for (_Static_assert(0, "ko"); 1; )
> 			;
> 	}
> 
> It should because (since C99) the first part of the for-statement
> is just a 'declaration', which include the static assert.
> Not that it's very important, though.
> 
> Probably, it's best to leave it as is for the moment and just
> add a new test case, annotated with 'check-known-to-fail'.
> 
> -- Luc
> 

Hi Luc,

I'm not sure it should be accepted; the standard doc says:

    "The declaration part of a for statement shall only declare
     identifiers for objects having storage class auto or register."
 
But _Static_assert() doesn't declare an identifier.

gcc accepts this syntax, although clang does not.  I did find this discussion:

    https://reviews.llvm.org/D9113

Which points to a working group discussion that made it sound as
though _Static_assert() should not be accepted in for-loop declarations:

    www.open-std.org/JTC1/SC22/WG14/13677

As you say, probably best to leave this for now.

   Lance

  reply	other threads:[~2017-05-04 15:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03 16:55 [PATCH v4] sparse: add support for _Static_assert Lance Richardson
2017-05-03 23:54 ` Luc Van Oostenryck
2017-05-04  2:29   ` Luc Van Oostenryck
2017-05-04 13:53     ` Lance Richardson
2017-05-04 14:58       ` Luc Van Oostenryck
2017-05-04 15:46         ` Lance Richardson [this message]
2017-05-04 16:29           ` Luc Van Oostenryck
2017-05-04  3:03 ` Christopher Li
2017-05-04 13:56   ` Lance Richardson

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=99956653.4916117.1493912815498.JavaMail.zimbra@redhat.com \
    --to=lrichard@redhat.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.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 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).