public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Peter Bergner <bergner@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc(refs/vendors/ibm/heads/gcc-10-branch)] Daily bump.
Date: Thu,  3 Sep 2020 16:39:01 +0000 (GMT)	[thread overview]
Message-ID: <20200903163901.8DA483986031@sourceware.org> (raw)

https://gcc.gnu.org/g:9aae0c155ff86530e139b372284a492dafe7cd56

commit 9aae0c155ff86530e139b372284a492dafe7cd56
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date:   Thu Aug 27 00:17:01 2020 +0000

    Daily bump.

Diff:
---
 gcc/ChangeLog          | 17 +++++++++++++++++
 gcc/DATESTAMP          |  2 +-
 libstdc++-v3/ChangeLog | 20 ++++++++++++++++++++
 3 files changed, 38 insertions(+), 1 deletion(-)

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 10ed17f1549..1eca4df0f59 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,20 @@
+2020-08-26  Roger Sayle  <roger@nextmovesoftware.com>
+
+	PR middle-end/87256
+	* config/pa/pa.c (hppa_rtx_costs_shadd_p): New helper function
+	to check for coefficients supported by shNadd and shladd,l.
+	(hppa_rtx_costs):  Rewrite to avoid using estimates based upon
+	FACTOR and enable recursing deeper into RTL expressions.
+	* config/pa/pa.md (shd_internal): Fix define_expand to provide
+	gen_shd_internal.
+
+2020-08-26  Roger Sayle  <roger@nextmovesoftware.com>
+
+	* config/pa/pa.md (ashldi3): Additionally, on !TARGET_64BIT
+	generate a two instruction shd/zdep sequence when shifting
+	registers by suitable constants.
+	(shd_internal): New define_expand to provide gen_shd_internal.
+
 2020-08-25  Jakub Jelinek  <jakub@redhat.com>
 
 	Backported from master:
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index 1aa5e58d9a2..c7ea9e023ae 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20200826
+20200827
diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog
index 6ec8b6bee25..80ed5e320ea 100644
--- a/libstdc++-v3/ChangeLog
+++ b/libstdc++-v3/ChangeLog
@@ -1,3 +1,23 @@
+2020-08-26  Jonathan Wakely  <jwakely@redhat.com>
+
+	Backported from master:
+	2020-08-26  Jonathan Wakely  <jwakely@redhat.com>
+
+	PR libstdc++/71960
+	* include/experimental/string_view (basic_string_view):
+	Enable debug assertions.
+	* include/std/string_view (basic_string_view):
+	Likewise.
+
+2020-08-26  Jonathan Wakely  <jwakely@redhat.com>
+
+	Backported from master:
+	2020-08-24  Jonathan Wakely  <jwakely@redhat.com>
+
+	PR libstdc++/96766
+	* include/std/variant (_Variant_storage): Replace implicit
+	conversions from size_t to __index_type with explicit casts.
+
 2020-08-21  Jonathan Wakely  <jwakely@redhat.com>
 
 	Backported from master:


             reply	other threads:[~2020-09-03 16:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03 16:39 Peter Bergner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-09-03 16:41 Peter Bergner
2020-09-03 16:37 Peter Bergner
2020-09-03 16:36 Peter Bergner
2020-08-19 13:59 Peter Bergner
2020-08-19 13:59 Peter Bergner
2020-08-19 13:58 Peter Bergner
2020-08-19 13:57 Peter Bergner
2020-07-23 19:00 Peter Bergner
2020-07-03  2:59 Peter Bergner
2020-07-02 21:09 Peter Bergner
2020-07-02 21:07 Peter Bergner
2020-07-02 21:05 Peter Bergner
2020-06-25  0:33 Peter Bergner
2020-06-25  0:28 Peter Bergner

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=20200903163901.8DA483986031@sourceware.org \
    --to=bergner@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: link
Be 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).