public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/102502] C11: _Static_assert disallows const int operand in -O0 while allows it in higher -O
Date: Mon, 27 Sep 2021 21:05:04 +0000	[thread overview]
Message-ID: <bug-102502-4-ErOQEmYhf2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102502-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102502

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #4)
> (In reply to Jakub Jelinek from comment #2)
> > Why do you think it is a bug?
> 
> Because there were other bugs which were fixed where there was an
> inconsistency, PR 66618, and PR 71983 for an example. There are others.
> 
> Oh there is an inconsistency when the _Static_assert is not in a function vs
> inside a function.
> Take:
> static const int allocation_size = 32768;
> _Static_assert (allocation_size, "");
> void f(void) { _Static_assert(allocation_size, ""); }
> 
> The assert inside the function is accepted at -O1 but reject at -O0 while
> the one outside is always rejected.

But it is an intentional decision, to match the previous behavior in that area
plus handle what was needed.

      parent reply	other threads:[~2021-09-27 21:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27 18:35 [Bug c/102502] New: " i at maskray dot me
2021-09-27 18:41 ` [Bug c/102502] " pinskia at gcc dot gnu.org
2021-09-27 18:55 ` jakub at gcc dot gnu.org
2021-09-27 19:53 ` i at maskray dot me
2021-09-27 20:54 ` pinskia at gcc dot gnu.org
2021-09-27 21:05 ` jakub at gcc dot gnu.org [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=bug-102502-4-ErOQEmYhf2@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).