public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tobias Burnus <burnus@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/omp/gcc-12] Merge branch 'releases/gcc-12' into devel/omp/gcc-12
Date: Thu,  2 Feb 2023 09:20:31 +0000 (GMT)	[thread overview]
Message-ID: <20230202092031.87D8F3857BA4@sourceware.org> (raw)

https://gcc.gnu.org/g:251c9fdb3bb59c2603b5db526eda1828badd768c

commit 251c9fdb3bb59c2603b5db526eda1828badd768c
Merge: 6b611f1b3ca d31bd713861
Author: Tobias Burnus <tobias@codesourcery.com>
Date:   Thu Feb 2 10:03:35 2023 +0100

    Merge branch 'releases/gcc-12' into devel/omp/gcc-12
    
    Merge up to r12-9097-gd31bd7138610a883310dce212bb0bdaaa8da7304 (2nd Feb 2023)

Diff:

 gcc/ChangeLog                                 | 22 ++++++++++++++++
 gcc/DATESTAMP                                 |  2 +-
 gcc/c-family/ChangeLog                        |  8 ++++++
 gcc/c-family/c-common.h                       |  1 +
 gcc/c-family/c-warn.cc                        |  2 +-
 gcc/c/ChangeLog                               |  6 +++++
 gcc/c/c-objc-common.cc                        |  8 ++++++
 gcc/cgraph.cc                                 | 14 ++++++++--
 gcc/cp/ChangeLog                              | 16 +++++++++++
 gcc/cp/call.cc                                |  2 +-
 gcc/cp/cp-tree.h                              |  1 -
 gcc/fortran/ChangeLog                         |  8 ++++++
 gcc/range-op.cc                               |  4 +--
 gcc/testsuite/ChangeLog                       | 21 +++++++++++++++
 gcc/testsuite/g++.dg/warn/Wduplicated-cond3.C | 38 +++++++++++++++++++++++++++
 gcc/testsuite/g++.dg/warn/Wduplicated-cond4.C | 17 ++++++++++++
 gcc/testsuite/g++.dg/warn/Wduplicated-cond5.C | 16 +++++++++++
 gcc/testsuite/g++.dg/warn/Wlogical-op-4.C     | 23 ++++++++++++++++
 gcc/testsuite/gcc.dg/pr108306.c               | 29 ++++++++++++++++++++
 libgomp/ChangeLog                             |  8 ++++++
 20 files changed, 238 insertions(+), 8 deletions(-)

             reply	other threads:[~2023-02-02  9:20 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02  9:20 Tobias Burnus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-02 15:33 Tobias Burnus
2023-02-27 16:34 Tobias Burnus
2023-02-20  6:52 Tobias Burnus
2023-02-13  9:21 Tobias Burnus
2023-02-06  7:42 Tobias Burnus
2023-01-30  9:11 Tobias Burnus
2023-01-26 10:22 Tobias Burnus
2023-01-23  8:29 Tobias Burnus
2023-01-19 20:24 Tobias Burnus
2023-01-16 11:27 Tobias Burnus
2023-01-09  9:21 Tobias Burnus
2022-12-27 10:54 Tobias Burnus
2022-12-21 18:21 Tobias Burnus
2022-12-19 17:32 Tobias Burnus
2022-12-12 14:26 Tobias Burnus
2022-12-09  8:39 Tobias Burnus
2022-12-01  7:40 Tobias Burnus
2022-11-25 10:37 Tobias Burnus
2022-11-21 14:29 Tobias Burnus
2022-11-18  9:48 Tobias Burnus
2022-11-14 15:41 Tobias Burnus
2022-11-04 12:50 Tobias Burnus
2022-11-02  8:07 Tobias Burnus
2022-10-27 12:39 Tobias Burnus
2022-10-24 10:21 Tobias Burnus
2022-10-18  9:12 Tobias Burnus
2022-10-11  8:26 Tobias Burnus
2022-09-29 14:45 Tobias Burnus
2022-09-28  7:53 Tobias Burnus
2022-09-23  8:48 Tobias Burnus
2022-09-09 13:39 Tobias Burnus
2022-09-05  8:19 Tobias Burnus
2022-08-31  6:14 Tobias Burnus
2022-08-03 12:17 Tobias Burnus
2022-08-01 13:03 Tobias Burnus
2022-07-28 13:29 Tobias Burnus
2022-07-28 13:29 Tobias Burnus
2022-07-05 10:32 Tobias Burnus
2022-07-01 18:13 Kwok Yeung

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=20230202092031.87D8F3857BA4@sourceware.org \
    --to=burnus@gcc.gnu.org \
    --cc=gcc-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).