public inbox for libstdc++-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: Mon, 22 Nov 2021 16:39:46 +0000 (GMT)	[thread overview]
Message-ID: <20211122163946.16BB93858426@sourceware.org> (raw)

https://gcc.gnu.org/g:44a06feaf84111c298bb906b4906b54073fc61d5

commit 44a06feaf84111c298bb906b4906b54073fc61d5
Merge: ffa33d36af9 c38c547a708
Author: Martin Liska <mliska@suse.cz>
Date:   Mon Nov 22 17:39:30 2021 +0100

    Merge branch 'master' into devel/sphinx

Diff:

 gcc/cp/parser.c                              | 26 ++++++--------
 gcc/doc/invoke.texi                          | 12 -------
 gcc/testsuite/c-c++-common/goacc/routine-6.c |  4 +++
 libgcc/unwind-dw2-fde-dip.c                  | 54 +++++++++++++++++++++-------
 libstdc++-v3/include/bits/c++config          |  4 +--
 5 files changed, 59 insertions(+), 41 deletions(-)


             reply	other threads:[~2021-11-22 16:39 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 16:39 Martin Liska [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-08 11:37 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 11:53 Martin Liska
2022-09-12  8:43 Martin Liska
2022-09-06  4:52 Martin Liska
2022-09-05  8:45 Martin Liska
2022-08-24  8:10 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-21 14:12 Martin Liska
2022-07-19 13:41 Martin Liska
2022-07-18  7:51 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: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 10:16 Martin Liska
2021-12-16 13:11 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 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 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-06 10:38 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-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 13:38 Martin Liska
2021-06-14  9:40 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-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-27  7:52 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

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=20211122163946.16BB93858426@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).