public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "i at maskray dot me" <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 19:53:07 +0000 [thread overview] Message-ID: <bug-102502-4-XujhLquWoB@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 #3 from Fangrui Song <i at maskray dot me> --- OK, Andrew asked me to file it :) I just wanted to fix glibc and run away from the GCC inconsistency. I know that https://www.iso-9899.info/n1570.html#6.6 p10 says "An implementation may accept other forms of constant expressions." Accepting `const int` in C mode is an extension, but it seems odd to be inconsistent (-O0 and -O2 -Wpedantic reject it while -O2 allows it). % cat reduce.i const int __alloc_dir_allocation_size = 8; void __alloc_dir() { _Static_assert(__alloc_dir_allocation_size, ""); } % gcc reduce.i -c -std=c11 reduce.i: In function ‘__alloc_dir’: reduce.i:2:37: error: expression in static assertion is not constant 2 | void __alloc_dir() { _Static_assert(__alloc_dir_allocation_size, ""); } | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ % gcc reduce.i -c -std=c11 -O1 % gcc reduce.i -c -std=c11 -O2 % gcc reduce.i -c -std=c11 -O2 -Wpedantic reduce.i: In function ‘__alloc_dir’: reduce.i:2:37: warning: expression in static assertion is not an integer constant expression [-Wpedantic] 2 | void __alloc_dir() { _Static_assert(__alloc_dir_allocation_size, ""); } | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ Clang just rejects it in all optimization levels. % clang reduce.i -c -std=c11 -O0 reduce.i:2:37: error: static_assert expression is not an integral constant expression void __alloc_dir() { _Static_assert(__alloc_dir_allocation_size, ""); } ^~~~~~~~~~~~~~~~~~~~~~~~~~~ 1 error generated. % clang reduce.i -c -std=c11 -O1 reduce.i:2:37: error: static_assert expression is not an integral constant expression void __alloc_dir() { _Static_assert(__alloc_dir_allocation_size, ""); } ^~~~~~~~~~~~~~~~~~~~~~~~~~~ 1 error generated.
next prev parent reply other threads:[~2021-09-27 19:53 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 [this message] 2021-09-27 20:54 ` pinskia at gcc dot gnu.org 2021-09-27 21:05 ` jakub at gcc dot gnu.org
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-XujhLquWoB@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: linkBe 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).