public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc/devel/sphinx] Merge branch 'master' into devel/sphinx
Date: Fri, 6 Aug 2021 10:38:29 +0000 (GMT) [thread overview]
Message-ID: <20210806103829.601B939B5869@sourceware.org> (raw)
https://gcc.gnu.org/g:01c909e1a5fca4988431a328454e9d8c0eea9ef6
commit 01c909e1a5fca4988431a328454e9d8c0eea9ef6
Merge: f182597d273 3c94db20be9
Author: Martin Liska <mliska@suse.cz>
Date: Fri Aug 6 12:38:10 2021 +0200
Merge branch 'master' into devel/sphinx
Diff:
gcc/ChangeLog | 96 ++
gcc/DATESTAMP | 2 +-
gcc/c/c-parser.c | 63 +-
gcc/config/aarch64/arm_neon.h | 1530 ++++++++++++++++----
gcc/config/rs6000/rs6000.c | 2 +
gcc/doc/invoke.texi | 80 +-
gcc/dominance.c | 4 +-
gcc/dominance.h | 2 +-
gcc/gcov-io.c | 36 +-
gcc/gcov-io.h | 1 +
gcc/go/gofrontend/MERGE | 2 +-
gcc/go/gofrontend/expressions.cc | 48 +-
gcc/ipa-prop.h | 8 +-
gcc/testsuite/ChangeLog | 82 ++
gcc/testsuite/gcc.dg/gcov-info-to-gcda.c | 60 +
.../aarch64/vector_structure_intrinsics.c | 76 +-
gcc/testsuite/gcc.target/powerpc/pragma-optimize.c | 13 +
gcc/testsuite/gfortran.dg/vect/vect-8.f90 | 3 +-
gcc/tree-data-ref.c | 10 +-
gcc/tree-data-ref.h | 4 +-
gcc/tree-predcom.c | 13 +-
gcc/tree-ssa-pre.c | 2 +-
gcc/tree-ssa-threadbackward.c | 6 +-
gcc/tree-vect-data-refs.c | 15 +-
gcc/tree-vect-slp-patterns.c | 2 +-
gcc/tree-vect-stmts.c | 2 +-
gcc/tree-vectorizer.h | 4 +-
gcc/vec.c | 47 +-
gcc/vec.h | 66 +-
libcpp/ChangeLog | 11 +
libgcc/ChangeLog | 7 +
libgcc/Makefile.in | 2 +-
libgcc/gcov.h | 19 +
libgcc/libgcov-driver.c | 187 ++-
libgcc/libgcov.h | 5 -
libgo/go/runtime/internal/atomic/atomic.c | 80 +
libgo/go/runtime/internal/atomic/stubs.go | 25 +
libgomp/ChangeLog | 31 +
libstdc++-v3/ChangeLog | 47 +
libstdc++-v3/include/bits/ranges_base.h | 24 +-
libstdc++-v3/include/bits/stl_iterator.h | 24 +-
libstdc++-v3/include/bits/stl_queue.h | 3 -
libstdc++-v3/include/std/ranges | 42 +-
43 files changed, 2217 insertions(+), 569 deletions(-)
next reply other threads:[~2021-08-06 10:38 UTC|newest]
Thread overview: 126+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 10:38 Martin Liska [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-08 11:37 Martin Liska
2022-11-07 8:55 Martin Liska
2022-11-07 7:25 Martin Liska
2022-10-28 8:02 Martin Liska
2022-10-26 10:59 Martin Liska
2022-10-21 10:48 Martin Liska
2022-10-19 13:25 Martin Liska
2022-10-17 8:20 Martin Liska
2022-10-15 13:33 Martin Liska
2022-10-13 13:54 Martin Liska
2022-10-08 8:19 Martin Liska
2022-10-04 10:05 Martin Liska
2022-09-29 8:41 Martin Liska
2022-09-26 19:06 Martin Liska
2022-09-20 15:24 Martin Liska
2022-09-20 12:03 Martin Liska
2022-09-20 11:53 Martin Liska
2022-09-12 8:43 Martin Liska
2022-09-06 4:52 Martin Liska
2022-09-05 9:22 Martin Liska
2022-09-05 8:45 Martin Liska
2022-08-24 8:10 Martin Liska
2022-08-10 7:18 Martin Liska
2022-08-09 13:30 Martin Liska
2022-08-08 7:05 Martin Liska
2022-08-01 3:54 Martin Liska
2022-07-26 12:28 Martin Liska
2022-07-26 12:09 Martin Liska
2022-07-26 8:04 Martin Liska
2022-07-25 7:01 Martin Liska
2022-07-21 14:12 Martin Liska
2022-07-19 13:41 Martin Liska
2022-07-18 7:51 Martin Liska
2022-07-14 9:34 Martin Liska
2022-07-14 8:35 Martin Liska
2022-07-14 8:23 Martin Liska
2022-07-12 11:24 Martin Liska
2022-07-10 14:45 Martin Liska
2022-06-17 11:35 Martin Liska
2022-06-17 11:06 Martin Liska
2022-03-15 9:13 Martin Liska
2022-03-10 9:42 Martin Liska
2022-03-06 15:29 Martin Liska
2022-01-28 13:08 Martin Liska
2022-01-24 12:35 Martin Liska
2022-01-20 12:38 Martin Liska
2022-01-18 14:25 Martin Liska
2022-01-12 12:35 Martin Liska
2022-01-03 19:33 Martin Liska
2022-01-03 10:16 Martin Liska
2021-12-30 13:34 Martin Liska
2021-12-29 12:43 Martin Liska
2021-12-28 10:14 Martin Liska
2021-12-28 10:06 Martin Liska
2021-12-22 11:17 Martin Liska
2021-12-22 11:08 Martin Liska
2021-12-22 11:03 Martin Liska
2021-12-20 10:01 Martin Liska
2021-12-17 14:04 Martin Liska
2021-12-16 14:23 Martin Liska
2021-12-16 13:11 Martin Liska
2021-12-13 10:57 Martin Liska
2021-12-12 21:22 Martin Liska
2021-12-09 10:39 Martin Liska
2021-12-01 12:31 Martin Liska
2021-11-25 12:26 Martin Liska
2021-11-23 10:28 Martin Liska
2021-11-22 16:39 Martin Liska
2021-11-22 12:58 Martin Liska
2021-11-16 14:50 Martin Liska
2021-10-21 9:51 Martin Liska
2021-10-18 12:43 Martin Liska
2021-08-27 8:52 Martin Liska
2021-08-26 9:23 Martin Liska
2021-08-24 14:43 Martin Liska
2021-08-24 7:30 Martin Liska
2021-08-23 13:42 Martin Liska
2021-08-23 10:35 Martin Liska
2021-08-19 10:03 Martin Liska
2021-08-18 14:13 Martin Liska
2021-08-10 7:12 Martin Liska
2021-08-09 9:15 Martin Liska
2021-08-05 17:50 Martin Liska
2021-08-03 13:50 Martin Liska
2021-07-12 9:41 Martin Liska
2021-06-30 4:49 Martin Liska
2021-06-29 6:49 Martin Liska
2021-06-28 11:11 Martin Liska
2021-06-25 8:52 Martin Liska
2021-06-24 14:10 Martin Liska
2021-06-23 8:20 Martin Liska
2021-06-22 7:48 Martin Liska
2021-06-21 7:33 Martin Liska
2021-06-17 10:06 Martin Liska
2021-06-16 12:19 Martin Liska
2021-06-15 12:35 Martin Liska
2021-06-14 14:08 Martin Liska
2021-06-14 14:05 Martin Liska
2021-06-14 13:38 Martin Liska
2021-06-14 9:40 Martin Liska
2021-06-11 11:03 Martin Liska
2021-06-10 6:22 Martin Liska
2021-06-09 11:40 Martin Liska
2021-06-08 7:47 Martin Liska
2021-06-07 13:38 Martin Liska
2021-06-06 14:57 Martin Liska
2021-06-04 11:37 Martin Liska
2021-06-03 10:53 Martin Liska
2021-06-02 12:46 Martin Liska
2021-06-02 6:59 Martin Liska
2021-05-31 9:31 Martin Liska
2021-05-28 12:29 Martin Liska
2021-05-27 7:52 Martin Liska
2021-05-26 7:35 Martin Liska
2021-05-26 7:29 Martin Liska
2021-05-25 13:01 Martin Liska
2021-05-24 9:40 Martin Liska
2021-05-18 9:25 Martin Liska
2021-05-17 13:53 Martin Liska
2021-05-11 17:33 Martin Liska
2021-04-22 7:11 Martin Liska
2021-04-20 8:02 Martin Liska
2021-04-19 11:44 Martin Liska
2021-04-15 12:51 Martin Liska
2021-04-14 10:30 Martin Liska
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=20210806103829.601B939B5869@sourceware.org \
--to=marxin@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).