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++/92978] std::gcd mishandles mixed-signedness Date: Wed, 02 Sep 2020 16:23:13 +0000 [thread overview] Message-ID: <bug-92978-4-p04vDXbw5e@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-92978-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92978 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:c71644776f4e8477289a4de16239dbb420db6945 commit r11-2983-gc71644776f4e8477289a4de16239dbb420db6945 Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed Sep 2 17:20:37 2020 +0100 libstdc++: Fix test to use correct function This was copied from a test for std::lcm but I forgot to change one of the calls to use the experimental version of the function. libstdc++-v3/ChangeLog: PR libstdc++/92978 * testsuite/experimental/numeric/92978.cc: Use experimental::lcm not std::lcm.
next prev parent reply other threads:[~2020-09-02 16:23 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-92978-4@http.gcc.gnu.org/bugzilla/> 2020-08-28 14:23 ` redi at gcc dot gnu.org 2020-08-28 22:11 ` cvs-commit at gcc dot gnu.org 2020-08-28 22:12 ` redi at gcc dot gnu.org 2020-09-02 16:23 ` cvs-commit at gcc dot gnu.org [this message] 2020-09-02 16:32 ` cvs-commit at gcc dot gnu.org 2020-09-21 23:14 ` cvs-commit at gcc dot gnu.org 2020-11-16 21:58 ` cvs-commit at gcc dot gnu.org 2020-11-16 21:59 ` redi at gcc dot gnu.org 2022-06-10 14:24 ` cvs-commit at gcc dot gnu.org 2022-08-03 13:46 ` cvs-commit at gcc dot gnu.org 2023-05-03 15:02 ` cvs-commit at gcc dot gnu.org 2023-05-03 16:34 ` 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-92978-4-p04vDXbw5e@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).