public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Gaius Mulley <gaius@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/modula-2] (10 commits) Merge branch 'master' into devel/modula-2.
Date: Sun, 14 Aug 2022 18:30:59 +0000 (GMT) [thread overview]
Message-ID: <20220814183059.EB0C73858D32@sourceware.org> (raw)
The branch 'devel/modula-2' was updated to point to:
ecba4ac8214... Merge branch 'master' into devel/modula-2.
It previously pointed to:
627be3b3ac5... Cleanup revert lang_register_spec_functions in all spec fil
Diff:
Summary of changes (added commits):
-----------------------------------
ecba4ac... Merge branch 'master' into devel/modula-2.
475ed8f... Daily bump. (*)
b748d46... [Committed] arm: Document +no options for Cortex-M55 CPU. (*)
0f2c7cc... Fix invalid devirtualization when combining final keyword a (*)
88ee126... Improve comment for tree_niter_desc.{control,bound,cmp} (*)
83e9bc7... phiopt: Remove unnecessary checks from spaceship_replacemen (*)
4cc0d3e... tree-optimization/106593 - fix ICE with backward threading (*)
f4ff20d... sve: Fix fcmuo combine patterns [PR106524] (*)
7e3b45b... analyzer: out-of-bounds checker [PR106000] (*)
2b75b3b... analyzer: consider that realloc could shrink the buffer [PR (*)
(*) This commit already exists in another branch.
Because the reference `refs/heads/devel/modula-2' matches
your hooks.email-new-commits-only configuration,
no separate email is sent for this commit.
next reply other threads:[~2022-08-14 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 18:30 Gaius Mulley [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-06 12:28 Gaius Mulley
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=20220814183059.EB0C73858D32@sourceware.org \
--to=gaius@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).