public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Peter Bergner <bergner@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/ibm/heads/gcc-11-branch] (15 commits) ibm: Merge up to top of releases/gcc-11
Date: Wed, 22 Sep 2021 13:23:46 +0000 (GMT) [thread overview]
Message-ID: <20210922132346.E0ECB3858D39@sourceware.org> (raw)
The branch 'ibm/heads/gcc-11-branch' was updated to point to:
ee1df65e923... ibm: Merge up to top of releases/gcc-11
It previously pointed to:
b2ff4cfc682... ibm: Merge up to top of releases/gcc-11
Diff:
Summary of changes (added commits):
-----------------------------------
ee1df65... ibm: Merge up to top of releases/gcc-11
ae362db... Daily bump. (*)
da0a562... rs6000: Fix ELFv2 r12 use in epilogue (*)
5210f05... rs6000: Don't use r12 for CR save on ELFv2 (PR102107) (*)
7fbab3a... Fortran - (large) arrays in the main shall be static (*)
d891ef6... Fix no_fsanitize_address effective target (*)
d4b84ae... Daily bump. (*)
b1dc26d... GCC11 - Fortran: combined directives - order(concurrent) no (*)
79c523d... Daily bump. (*)
6527feb... Fortran - fix handling of optional allocatable DT arguments (*)
1ae01a8... Fortran - fix ICE during error recovery checking entry char (*)
0d2d24f... Daily bump. (*)
7026df8... Daily bump. (*)
469aad8... Fix PR rtl-optimization/102306 (*)
a6aa245... Daily bump. (*)
(*) This commit already exists in another branch.
Because the reference `refs/vendors/ibm/heads/gcc-11-branch' matches
your hooks.email-new-commits-only configuration,
no separate email is sent for this commit.
next reply other threads:[~2021-09-22 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 13:23 Peter Bergner [this message]
2023-05-02 17:40 Peter Bergner
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=20210922132346.E0ECB3858D39@sourceware.org \
--to=bergner@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).