public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: GCC Administrator <gccadmin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r13-5819] Daily bump.
Date: Sun, 12 Feb 2023 00:18:31 +0000 (GMT)	[thread overview]
Message-ID: <20230212001831.86F4E3858D32@sourceware.org> (raw)

https://gcc.gnu.org/g:ee1178878383ddd64e760f17338fe8a8384c31c8

commit r13-5819-gee1178878383ddd64e760f17338fe8a8384c31c8
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date:   Sun Feb 12 00:17:22 2023 +0000

    Daily bump.

Diff:
---
 gcc/ChangeLog           | 11 +++++++++++
 gcc/DATESTAMP           |  2 +-
 gcc/testsuite/ChangeLog | 17 +++++++++++++++++
 libiberty/ChangeLog     |  5 +++++
 libstdc++-v3/ChangeLog  |  6 ++++++
 5 files changed, 40 insertions(+), 1 deletion(-)

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index a18f560d4e1..2c4867cfcd1 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,14 @@
+2023-02-11  Jakub Jelinek  <jakub@redhat.com>
+
+	PR ipa/108605
+	* ipa-cp.cc (ipa_agg_value_from_jfunc): Return NULL_TREE also if
+	item->offset bit position is too large to be representable as
+	unsigned int byte position.
+
+2023-02-11  Gerald Pfeifer  <gerald@pfeifer.com>
+
+	* doc/extend.texi (Other Builtins): Adjust link to WG14 N965.
+
 2023-02-10  Vladimir N. Makarov  <vmakarov@redhat.com>
 
 	* ira.cc (update_equiv_regs): Set up ira_reg_equiv for
diff --git a/gcc/DATESTAMP b/gcc/DATESTAMP
index 9f537e04ede..d696f4e8b1a 100644
--- a/gcc/DATESTAMP
+++ b/gcc/DATESTAMP
@@ -1 +1 @@
-20230211
+20230212
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index f188e5fbde3..577b8fd48d8 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,20 @@
+2023-02-11  Jakub Jelinek  <jakub@redhat.com>
+
+	PR ipa/108605
+	* c-c++-common/pr108605.c: New test.
+
+2023-02-11  Jonathan Yong  <10walls@gmail.com>
+
+	* gcc.dg/pr65658.c: fix LLP64 test.
+
+2023-02-11  Jonathan Yong  <10walls@gmail.com>
+
+	* c-c++-common/Wsizeof-array-div1.c: fix excess warnings.
+	* gcc.dg/Warray-bounds-52.c: ditto
+	* gcc.dg/Wstringop-overflow-62.c: ditto
+	* gcc.dg/attr-vector_size.c: ditto
+	* gcc.dg/overflow-warn-9.c: ditto
+
 2023-02-10  David Malcolm  <dmalcolm@redhat.com>
 
 	PR analyzer/108745
diff --git a/libiberty/ChangeLog b/libiberty/ChangeLog
index f11fff19c2b..3f0e4cfadc2 100644
--- a/libiberty/ChangeLog
+++ b/libiberty/ChangeLog
@@ -1,3 +1,8 @@
+2023-02-11  niXman  <i.nixman@autistici.org>
+
+	* lrealpath.c (lrealpath): try to resolve symlink and
+	use UNC paths where applicable.
+
 2023-01-07  LIU Hao  <lh_mouse@126.com>
 
 	PR middle-end/108300
diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog
index b9f041b641e..b0f79c079f9 100644
--- a/libstdc++-v3/ChangeLog
+++ b/libstdc++-v3/ChangeLog
@@ -1,3 +1,9 @@
+2023-02-11  Gerald Pfeifer  <gerald@pfeifer.com>
+
+	* doc/xml/manual/policy_data_structures_biblio.xml: Update
+	link to "Worst-case efficient priority queues".
+	* doc/html/manual/policy_data_structures.html: Regenerate.
+
 2023-02-06  Arsen Arsenović  <arsen@aarsen.me>
 
 	* doc/xml/manual/using.xml: Document newly-freestanding

                 reply	other threads:[~2023-02-12  0:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230212001831.86F4E3858D32@sourceware.org \
    --to=gccadmin@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).