public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/redhat/heads/gcc-13-branch] (18 commits) Merge commit 'r13-7249-gd2e0b6a3c4965635d8ba8e217ef2272e7be
Date: Wed, 26 Apr 2023 08:44:39 +0000 (GMT) [thread overview]
Message-ID: <20230426084439.3433C385843E@sourceware.org> (raw)
The branch 'redhat/heads/gcc-13-branch' was updated to point to:
99aa4c60d1f... Merge commit 'r13-7249-gd2e0b6a3c4965635d8ba8e217ef2272e7be
It previously pointed to:
4be14f2db84... Merge commit 'r13-7232-gc5bfb2e08bd551539a2a6c686cf3020b1e8
Diff:
Summary of changes (added commits):
-----------------------------------
99aa4c6... Merge commit 'r13-7249-gd2e0b6a3c4965635d8ba8e217ef2272e7be
d2e0b6a... Remove obsolete configure code in gnattools (*)
60e0164... testsuite: Fix up ext-floating2.C on powerpc64-linux (*)
4aeefba... testsuite: Fix up ext-floating15.C tests on powerpc64-linux (*)
f8646b8... c: Avoid -Wenum-int-mismatch warning for redeclaration of b (*)
2295ad5... Bump BASE-VER (*)
cc035c5... Update ChangeLog and version files for release (*)
789ff93... Update gennews for GCC 13. (*)
331a001... Daily bump. (*)
66829f0... Regenerate gcc.pot (*)
fb4e50a... powerpc: Fix up *branch_anddi3_dot for -m32 -mpowerpc64 [PR (*)
4fee426... Daily bump. (*)
bf30638... Update gcc hr.po, sv.po, zh_CN.po (*)
1cf9c91... doc: Update install.texi for GCC 13 (*)
f743863... Daily bump. (*)
1b67c6f... Daily bump. (*)
9b6bf07... match.pd: Fix fneg/fadd optimization [PR109583] (*)
19c8d72... Daily bump. (*)
(*) This commit already exists in another branch.
Because the reference `refs/vendors/redhat/heads/gcc-13-branch' matches
your hooks.email-new-commits-only configuration,
no separate email is sent for this commit.
reply other threads:[~2023-04-26 8:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230426084439.3433C385843E@sourceware.org \
--to=jakub@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).