public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/106988] New: subscripting a string literal is not an integer constant expression but __builtin_strlen is Date: Tue, 20 Sep 2022 20:27:55 +0000 [thread overview] Message-ID: <bug-106988-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106988 Bug ID: 106988 Summary: subscripting a string literal is not an integer constant expression but __builtin_strlen is Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: msebor at gcc dot gnu.org Target Milestone: --- In C mode, GCC rejects a subscript expression whose operand is a string literal in contexts where an integer constant expression is required but accepts an equivalent expression involving __builtin_strlen. Although conforming, it's inconsistent and unnecessarily restrictive. Accepting both (either with -Wpedantic) would also be conforming and more useful to programmers who need it but don't think of using the built-in workaround. $ cat a.c && gcc -S -Wall -Wpedantic a.c #define EMPTY1(S) (__builtin_strlen(S) == 0) _Static_assert(!EMPTY1("1"), ""); // ok #define EMPTY2(S) (S[0] == 0) _Static_assert(!EMPTY2("1"), ""); // error a.c:5:16: error: expression in static assertion is not constant 5 | _Static_assert(!EMPTY2("1"), ""); // error | ^
next reply other threads:[~2022-09-20 20:27 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-20 20:27 msebor at gcc dot gnu.org [this message] 2022-09-21 0:57 ` [Bug c/106988] " pinskia at gcc dot gnu.org 2022-09-22 16:12 ` msebor 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-106988-4@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).