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++/115454] std::experimental::find_last_set is buggy on x86-64-v4 Date: Thu, 27 Jun 2024 11:16:51 +0000 [thread overview] Message-ID: <bug-115454-4-Cp0XeoE3yo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115454-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115454 --- Comment #9 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-14 branch has been updated by Alexandre Oliva <aoliva@gcc.gnu.org>: https://gcc.gnu.org/g:b70af0bd2e33e9cc20dae45c131429a402fc8845 commit r14-10352-gb70af0bd2e33e9cc20dae45c131429a402fc8845 Author: Alexandre Oliva <oliva@adacore.com> Date: Thu Jun 27 08:14:34 2024 -0300 [libstdc++] [testsuite] defer to check_vect_support* [PR115454] The newly-added testcase overrides the default dg-do action set by check_vect_support_and_set_flags (in libstdc++-dg/conformance.exp), so it attempts to run the test even if runtime vector support is not available. Remove the explicit dg-do directive, so that the default is honored, and the test is run if vector support is found, and only compiled otherwise. for libstdc++-v3/ChangeLog PR libstdc++/115454 * testsuite/experimental/simd/pr115454_find_last_set.cc: Defer to check_vect_support_and_set_flags's default dg-do action. (cherry picked from commit 95faa1bea7bdc7f92fcccb3543bfcbc8184c5e5b)
next prev parent reply other threads:[~2024-06-27 11:16 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-12 3:16 [Bug libstdc++/115454] New: " lee.imple at gmail dot com 2024-06-13 12:17 ` [Bug libstdc++/115454] " mkretz at gcc dot gnu.org 2024-06-14 13:45 ` mkretz at gcc dot gnu.org 2024-06-14 13:48 ` mkretz at gcc dot gnu.org 2024-06-20 10:57 ` cvs-commit at gcc dot gnu.org 2024-06-20 18:41 ` cvs-commit at gcc dot gnu.org 2024-06-20 18:44 ` cvs-commit at gcc dot gnu.org 2024-06-21 16:25 ` cvs-commit at gcc dot gnu.org 2024-06-21 16:26 ` cvs-commit at gcc dot gnu.org 2024-06-27 10:24 ` cvs-commit at gcc dot gnu.org 2024-06-27 11:16 ` cvs-commit at gcc dot gnu.org [this message] 2024-06-27 11:33 ` cvs-commit at gcc dot gnu.org 2024-06-27 11:46 ` 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-115454-4-Cp0XeoE3yo@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).