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, 26 Jan 2023 10:22:40 +0000 (GMT) [thread overview] Message-ID: <20230126102240.48BD73858416@sourceware.org> (raw) https://gcc.gnu.org/g:8ab86cf46323bf769a59a2b56d3b5803d668b8cd commit 8ab86cf46323bf769a59a2b56d3b5803d668b8cd Merge: 04efab558b8 6484fc2bf68 Author: Tobias Burnus <tobias@codesourcery.com> Date: Thu Jan 26 11:08:00 2023 +0100 Merge branch 'releases/gcc-12' into devel/omp/gcc-12 Merge up to r12-9069-g6484fc2bf682ccf50c11675773cf72d32a079426 (26th Jan 2023) Diff: gcc/ChangeLog | 80 +++++++++++++ gcc/DATESTAMP | 2 +- gcc/config/aarch64/aarch64.cc | 28 +++-- gcc/fortran/ChangeLog | 10 ++ gcc/fortran/expr.cc | 4 +- gcc/function.cc | 5 + gcc/function.h | 2 + gcc/gcc.cc | 2 +- gcc/gimplify.cc | 6 +- gcc/testsuite/ChangeLog | 64 +++++++++++ .../bitfield-abi-warning-align16-O2-extra.C | 86 ++++++++++++++ .../aarch64/bitfield-abi-warning-align16-O2.C | 87 ++++++++++++++ .../bitfield-abi-warning-align32-O2-extra.C | 119 ++++++++++++++++++++ .../aarch64/bitfield-abi-warning-align32-O2.C | 119 ++++++++++++++++++++ .../aarch64/bitfield-abi-warning-align8-O2.C | 16 +++ .../g++.target/aarch64/bitfield-abi-warning.h | 125 +++++++++++++++++++++ gcc/testsuite/gcc.dg/pr107554.c | 12 ++ gcc/testsuite/gcc.dg/pr108164.c | 19 ++++ gcc/testsuite/gcc.dg/torture/pr108076.c | 17 +++ .../bitfield-abi-warning-align16-O2-extra.c | 86 ++++++++++++++ .../aarch64/bitfield-abi-warning-align16-O2.c | 87 ++++++++++++++ .../bitfield-abi-warning-align32-O2-extra.c | 119 ++++++++++++++++++++ .../aarch64/bitfield-abi-warning-align32-O2.c | 119 ++++++++++++++++++++ .../aarch64/bitfield-abi-warning-align8-O2.c | 16 +++ .../gcc.target/aarch64/bitfield-abi-warning.h | 125 +++++++++++++++++++++ gcc/testsuite/gfortran.dg/pr108434.f90 | 11 ++ gcc/tree-if-conv.cc | 14 ++- gcc/tree-ssa-strlen.cc | 2 +- gcc/tree-vect-loop-manip.cc | 12 +- 29 files changed, 1373 insertions(+), 21 deletions(-)
next reply other threads:[~2023-01-26 10:22 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-26 10:22 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-02-02 9:20 Tobias Burnus 2023-01-30 9:11 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=20230126102240.48BD73858416@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: linkBe 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).