public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "magnus.hegdahl at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/112795] New: [C++>=14] ICE pragma GCC unroll (n) cxx_eval_constant_expression Date: Thu, 30 Nov 2023 23:20:05 +0000 [thread overview] Message-ID: <bug-112795-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112795 Bug ID: 112795 Summary: [C++>=14] ICE pragma GCC unroll (n) cxx_eval_constant_expression Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: magnus.hegdahl at gmail dot com Target Milestone: --- Compiling the following code with GCC >= 8.1 (when #pragma GCC unroll was added), and -std=c++14 or higher results in an internal compiler error: ``` constexpr int n = 1; template <class = void> void f() { #pragma GCC unroll(n) for (int i = 0; i != n; ++i) { } } ``` It does not fail if f is not a template, if n is not parenthesized, or if using -std=c++11.
next reply other threads:[~2023-11-30 23:20 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-30 23:20 magnus.hegdahl at gmail dot com [this message] 2023-11-30 23:34 ` [Bug c++/112795] " magnus.hegdahl at gmail dot com 2023-12-01 14:10 ` mpolacek at gcc dot gnu.org 2023-12-01 15:22 ` jakub at gcc dot gnu.org 2023-12-01 15:55 ` jakub at gcc dot gnu.org 2023-12-01 17:13 ` ebotcazou at gcc dot gnu.org 2023-12-04 8:01 ` cvs-commit at gcc dot gnu.org 2023-12-04 8:02 ` jakub at gcc dot gnu.org 2023-12-05 16:32 ` cvs-commit at gcc dot gnu.org 2023-12-05 21:55 ` cvs-commit at gcc dot gnu.org 2023-12-05 22:38 ` jakub at gcc dot gnu.org 2023-12-16 0:37 ` cvs-commit at gcc dot gnu.org 2023-12-17 13:55 ` 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-112795-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).