public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit 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: Thu, 25 May 2023 07:05:19 +0000 [thread overview] Message-ID: <bug-109261-4-qoHUPPaTdp@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 --- Comment #18 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Matthias Kretz <mkretz@gcc.gnu.org>: https://gcc.gnu.org/g:ad27280442d7979cf9da03d59268919fecfd12f4 commit r11-10822-gad27280442d7979cf9da03d59268919fecfd12f4 Author: Matthias Kretz <m.kretz@gsi.de> Date: Wed May 24 12:50:46 2023 +0200 libstdc++: Fix SFINAE for __is_intrinsic_type on ARM On ARM NEON doesn't support double, so __is_intrinsic_type_v<double, whatever> should say false (instead of being ill-formed). Signed-off-by: Matthias Kretz <m.kretz@gsi.de> libstdc++-v3/ChangeLog: PR libstdc++/109261 * include/experimental/bits/simd.h (__intrinsic_type): Specialize __intrinsic_type<double, 8> and __intrinsic_type<double, 16> in any case, but provide the member type only with __aarch64__. (cherry picked from commit aa8b363171a95b8f867a74f29c75f9577e9087e1)
next prev parent reply other threads:[~2023-05-25 7:05 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 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 [this message] 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-qoHUPPaTdp@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).