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] [C++>=14] ICE pragma GCC unroll (n) cxx_eval_constant_expression Date: Thu, 30 Nov 2023 23:34:00 +0000 [thread overview] Message-ID: <bug-112795-4-lzu0KWLAJZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112795-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112795 --- Comment #1 from Magnus Hokland Hegdahl <magnus.hegdahl at gmail dot com> --- Full output: // Target: x86_64-pc-linux-gnu // Configured with: /build/gcc/src/gcc/configure --enable-languages=ada,c,c++,d,fortran,go,lto,objc,obj-c++ --enable-bootstrap --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --with-build-config=bootstrap-lto --with-linker-hash-style=gnu --with-system-zlib --enable-__cxa_atexit --enable-cet=auto --enable-checking=release --enable-clocale=gnu --enable-default-pie --enable-default-ssp --enable-gnu-indirect-function --enable-gnu-unique-object --enable-libstdcxx-backtrace --enable-link-serialization=1 --enable-linker-build-id --enable-lto --enable-multilib --enable-plugin --enable-shared --enable-threads=posix --disable-libssp --disable-libstdcxx-pch --disable-werror // Thread model: posix // Supported LTO compression algorithms: zlib zstd // gcc version 13.2.1 20230801 (GCC) // // mwe.cpp: In function ‘void f()’: // mwe.cpp:5:21: internal compiler error: in cxx_eval_constant_expression, at cp/constexpr.cc:7619 // 5 | #pragma GCC unroll(n) // | ^ // 0x1ad33c8 internal_error(char const*, ...) // ???:0 // 0x6b7b63 fancy_abort(char const*, int, char const*) // ???:0 // 0x711364 maybe_constant_value(tree_node*, tree_node*, mce_value) // ???:0 // 0x9443d0 c_common_parse_file() // ???:0 // Please submit a full bug report, with preprocessed source. // Please include the complete backtrace with any bug report. // See <https://bugs.archlinux.org/> for instructions. // /usr/lib/gcc/x86_64-pc-linux-gnu/13.2.1/cc1plus -quiet -D_GNU_SOURCE mwe.cpp -quiet -dumpbase mwe.cpp -dumpbase-ext .cpp -mtune=generic -march=x86-64 -Wall -Wextra -Wpedantic -freport-bug -o - -frandom-seed=0 -fdump-noaddr # 0 "mwe.cpp" # 0 "<built-in>" # 0 "<command-line>" # 1 "/usr/include/stdc-predef.h" 1 3 4 # 0 "<command-line>" 2 # 1 "mwe.cpp" constexpr int n = 1; template <class = void> void f() { #pragma GCC unroll(n) for (int i = 0; i != n; ++i) { } }
next prev parent reply other threads:[~2023-11-30 23:34 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-30 23:20 [Bug c++/112795] New: " magnus.hegdahl at gmail dot com 2023-11-30 23:34 ` magnus.hegdahl at gmail dot com [this message] 2023-12-01 14:10 ` [Bug c++/112795] " 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-lzu0KWLAJZ@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).