public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "johelegp at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107939] [11/12/13 Regression] Rejects use of `extern const` variable in a template Date: Wed, 30 Nov 2022 19:36:34 +0000 [thread overview] Message-ID: <bug-107939-4-pFHNrzz9No@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107939-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107939 --- Comment #2 from Johel Ernesto Guerrero Peña <johelegp at gmail dot com> --- Making the expression using the `extern const` variable more complex or indirect makes it work. With an IILE, for example: https://compiler-explorer.com/z/EjYYvPvqT.
next prev parent reply other threads:[~2022-11-30 19:36 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-30 19:32 [Bug c++/107939] New: " johelegp at gmail dot com 2022-11-30 19:35 ` [Bug c++/107939] [11/12/13 Regression] " pinskia at gcc dot gnu.org 2022-11-30 19:36 ` johelegp at gmail dot com [this message] 2022-12-01 8:04 ` rguenth at gcc dot gnu.org 2022-12-02 14:19 ` [Bug c++/107939] [11/12/13 Regression] Rejects use of `extern const` variable in a template since r11-557 jakub at gcc dot gnu.org 2023-03-02 22:48 ` mpolacek at gcc dot gnu.org 2023-03-03 0:02 ` mpolacek at gcc dot gnu.org 2023-03-03 16:35 ` mpolacek at gcc dot gnu.org 2023-03-07 15:13 ` cvs-commit at gcc dot gnu.org 2023-03-07 15:16 ` [Bug c++/107939] [11/12 " mpolacek at gcc dot gnu.org 2023-03-07 15:25 ` cvs-commit at gcc dot gnu.org 2023-03-07 15:25 ` [Bug c++/107939] [11 " mpolacek at gcc dot gnu.org 2023-11-16 14:32 ` cvs-commit at gcc dot gnu.org 2023-11-24 16:56 ` cvs-commit at gcc dot gnu.org 2023-11-27 22:02 ` cvs-commit 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-107939-4-pFHNrzz9No@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).