public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Iain D Sandoe <iains@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc/devel/c++-coroutines] Daily bump. Date: Mon, 31 Aug 2020 19:49:23 +0000 (GMT) [thread overview] Message-ID: <20200831194923.F406C3846079@sourceware.org> (raw) https://gcc.gnu.org/g:daba4a713e71eee7921df7a8040ea29032c1d0bc commit daba4a713e71eee7921df7a8040ea29032c1d0bc Author: GCC Administrator <gccadmin@gcc.gnu.org> Date: Sun Aug 30 00:16:20 2020 +0000 Daily bump. Diff: --- gcc/ChangeLog | 6 ++++++ gcc/DATESTAMP | 2 +- libstdc++-v3/ChangeLog | 8 ++++++++ 3 files changed, 15 insertions(+), 1 deletion(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 6d9084327a2..aeafff462a5 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,9 @@ +2020-08-29 Bill Schmidt <wschmidt@linux.ibm.com> + + * config/rs6000/rs6000-builtin.def (MASK_FOR_STORE): Remove. + * config/rs6000/rs6000-call.c (rs6000_expand_builtin): Remove + all logic for ALTIVEC_BUILTIN_MASK_FOR_STORE. + 2020-08-28 Martin Sebor <msebor@redhat.com> * attribs.c (init_attr_rdwr_indices): Use global access_mode. diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP index cb50c2bdf0d..cf802bc822d 100644 --- a/gcc/DATESTAMP +++ b/gcc/DATESTAMP @@ -1 +1 @@ -20200829 +20200830 diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index fa32bdee105..fa62ff9f381 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,11 @@ +2020-08-29 Jonathan Wakely <jwakely@redhat.com> + + * include/std/numeric (__detail::__absu(bool)): Make deleted + function a function template, so it will be chosen for calls + with an explicit template argument list. + * testsuite/26_numerics/gcd/gcd_neg.cc: Add dg-prune-output. + * testsuite/26_numerics/lcm/lcm_neg.cc: Likewise. + 2020-08-28 Jonathan Wakely <jwakely@redhat.com> * include/std/chrono (common_type): Fix partial specializations
next reply other threads:[~2020-08-31 19:49 UTC|newest] Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-31 19:49 Iain D Sandoe [this message] -- strict thread matches above, loose matches on Subject: below -- 2020-09-04 19:48 Iain D Sandoe 2020-09-03 20:10 Iain D Sandoe 2020-09-02 20:09 Iain D Sandoe 2020-08-31 19:49 Iain D Sandoe 2020-08-28 19:44 Iain D Sandoe 2020-08-27 19:17 Iain D Sandoe 2020-08-26 20:27 Iain D Sandoe 2020-08-25 20:00 Iain D Sandoe 2020-08-25 19:58 Iain D Sandoe 2020-08-21 19:30 Iain D Sandoe 2020-08-21 6:49 Iain D Sandoe 2020-08-19 19:18 Iain D Sandoe 2020-08-18 18:56 Iain D Sandoe 2020-08-17 19:25 Iain D Sandoe 2020-08-14 19:25 Iain D Sandoe 2020-08-13 20:07 Iain D Sandoe 2020-08-12 19:22 Iain D Sandoe 2020-08-11 20:04 Iain D Sandoe 2020-08-10 19:28 Iain D Sandoe 2020-08-07 19:50 Iain D Sandoe 2020-08-06 19:45 Iain D Sandoe 2020-08-03 19:48 Iain D Sandoe 2020-08-03 19:47 Iain D Sandoe 2020-07-31 20:48 Iain D Sandoe 2020-07-30 19:53 Iain D Sandoe 2020-07-29 20:54 Iain D Sandoe 2020-07-28 19:54 Iain D Sandoe 2020-07-23 19:39 Iain D Sandoe 2020-07-21 18:47 Iain D Sandoe 2020-07-20 20:40 Iain D Sandoe 2020-07-15 18:27 Iain D Sandoe 2020-07-14 18:42 Iain D Sandoe 2020-07-09 19:58 Iain D Sandoe 2020-07-08 19:00 Iain D Sandoe 2020-07-07 20:46 Iain D Sandoe 2020-07-03 22:04 Iain D Sandoe 2020-07-02 20:32 Iain D Sandoe 2020-06-30 18:35 Iain D Sandoe 2020-06-29 19:18 Iain D Sandoe 2020-06-25 20:47 Iain D Sandoe 2020-06-24 23:01 Iain D Sandoe 2020-06-23 19:13 Iain D Sandoe 2020-06-23 19:12 Iain D Sandoe 2020-06-23 19:11 Iain D Sandoe 2020-06-23 19:10 Iain D Sandoe 2020-06-18 19:10 Iain D Sandoe 2020-06-17 20:02 Iain D Sandoe 2020-06-16 19:48 Iain D Sandoe 2020-06-15 20:12 Iain D Sandoe 2020-06-12 18:45 Iain D Sandoe 2020-06-11 20:04 Iain D Sandoe 2020-06-10 23:24 Iain D Sandoe 2020-06-09 20:54 Iain D Sandoe 2020-06-05 19:34 Iain D Sandoe 2020-06-03 20:05 Iain D Sandoe 2020-06-02 18:47 Iain D Sandoe 2020-06-01 20:07 Iain D Sandoe 2020-06-01 20:05 Iain D Sandoe 2020-05-28 20:02 Iain D Sandoe 2020-05-27 19:53 Iain D Sandoe
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=20200831194923.F406C3846079@sourceware.org \ --to=iains@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@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).