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++/91153] New test case 29_atomics/atomic_float/1.cc execution test fails Date: Thu, 02 Jul 2020 18:58:11 +0000 [thread overview] Message-ID: <bug-91153-4-Gx3FAL5Vds@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-91153-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91153 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:14d4e7bc303a92f620eddcba9cef88da7e91514c commit r10-8416-g14d4e7bc303a92f620eddcba9cef88da7e91514c Author: Jonathan Wakely <jwakely.gcc@gmail.com> Date: Thu Jul 2 17:11:10 2020 +0000 libstdc++: Fix atomic<long double> tests (PR 91153, PR 93224) These tests fail with AIX double double. Use different floating point values that behave less surprisingly. libstdc++-v3/ChangeLog: PR libstdc++/91153 PR target/93224 * testsuite/29_atomics/atomic_float/1.cc: Use different values for tests. * testsuite/29_atomics/atomic_ref/float.cc: Likewise. (cherry picked from commit c6f431bba531bac3212b66069cf0f9718edf0132)
next prev parent reply other threads:[~2020-07-02 18:58 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-91153-4@http.gcc.gnu.org/bugzilla/> 2020-04-15 13:24 ` wschmidt at gcc dot gnu.org 2020-04-15 13:27 ` jakub at gcc dot gnu.org 2020-04-15 13:55 ` redi at gcc dot gnu.org 2020-04-15 14:55 ` wschmidt at gcc dot gnu.org 2020-07-02 18:08 ` cvs-commit at gcc dot gnu.org 2020-07-02 18:58 ` cvs-commit at gcc dot gnu.org [this message] 2020-07-02 18:59 ` redi 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-91153-4-Gx3FAL5Vds@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).