public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/109261] std::experimental::simd is not usable in several constant expressions Date: Tue, 23 May 2023 15:14:18 +0000 [thread overview] Message-ID: <bug-109261-4-KjdegKofns@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109261-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109261 Christophe Lyon <clyon at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |clyon at gcc dot gnu.org --- Comment #4 from Christophe Lyon <clyon at gcc dot gnu.org> --- The new testcase fails on arm and aarch64. For instance on arm, the log shows: /libstdc++-v3/testsuite/experimental/simd/pr109261_constexpr_simd.cc:45: error: non-constant condition for static assertion /libstdc++-v3/testsuite/experimental/simd/pr109261_constexpr_simd.cc:46: error: non-constant condition for static assertion /libstdc++-v3/testsuite/experimental/simd/pr109261_constexpr_simd.cc:56: error: non-constant condition for static assertion /libstdc++-v3/testsuite/experimental/simd/pr109261_constexpr_simd.cc:56: error: 'constexpr _Tp std::experimental::parallelism_v2::hmin(const simd<_Tp, _Ap>&) [with _Tp = char; _Abi = simd_abi::_VecBuiltin<16>]' called in a constant expression /libstdc++-v3/testsuite/experimental/simd/pr109261_constexpr_simd.cc:57: error: non-constant condition for static assertion /libstdc++-v3/testsuite/experimental/simd/pr109261_constexpr_simd.cc:57: error: 'constexpr _Tp std::experimental::parallelism_v2::hmax(const simd<_Tp, _Ap>&) [with _Tp = char; _Abi = simd_abi::_VecBuiltin<16>]' called in a constant expression
next prev parent reply other threads:[~2023-05-23 15:14 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-23 10:02 [Bug libstdc++/109261] New: " mkretz at gcc dot gnu.org 2023-03-23 10:02 ` [Bug libstdc++/109261] " mkretz at gcc dot gnu.org 2023-04-26 6:58 ` rguenth at gcc dot gnu.org 2023-05-23 7:27 ` cvs-commit at gcc dot gnu.org 2023-05-23 10:03 ` cvs-commit at gcc dot gnu.org 2023-05-23 15:14 ` clyon at gcc dot gnu.org [this message] 2023-05-23 15:37 ` mkretz at gcc dot gnu.org 2023-05-23 16:19 ` clyon at gcc dot gnu.org 2023-05-23 22:08 ` mkretz at gcc dot gnu.org 2023-05-24 8:28 ` clyon at gcc dot gnu.org 2023-05-24 11:06 ` cvs-commit at gcc dot gnu.org 2023-05-24 11:06 ` cvs-commit at gcc dot gnu.org 2023-05-24 12:31 ` clyon at gcc dot gnu.org 2023-05-24 19:41 ` cvs-commit at gcc dot gnu.org 2023-05-24 19:41 ` cvs-commit at gcc dot gnu.org 2023-05-25 7:03 ` cvs-commit at gcc dot gnu.org 2023-05-25 7:03 ` cvs-commit at gcc dot gnu.org 2023-05-25 7:04 ` cvs-commit at gcc dot gnu.org 2023-05-25 7:05 ` cvs-commit at gcc dot gnu.org 2023-05-25 7:05 ` cvs-commit at gcc dot gnu.org 2023-05-25 7:05 ` cvs-commit at gcc dot gnu.org 2023-05-25 7:07 ` mkretz 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-109261-4-KjdegKofns@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).