public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/sphinx] (16 commits) Merge branch 'master' into devel/sphinx
Date: Tue, 26 Jul 2022 08:04:13 +0000 (GMT) [thread overview]
Message-ID: <20220726080413.98C5B3858CDA@sourceware.org> (raw)
The branch 'devel/sphinx' was updated to point to:
8f694e3f186... Merge branch 'master' into devel/sphinx
It previously pointed to:
9630093982a... Merge branch 'master' into devel/sphinx
Diff:
Summary of changes (added commits):
-----------------------------------
8f694e3... Merge branch 'master' into devel/sphinx
bb04f9f... tree-optimization/106189 - avoid division by zero exception (*)
16fc26d... LoongArch: Support split symbol. (*)
d5e401f... LoongArch: Subdivision symbol type, add SYMBOL_PCREL suppor (*)
f428660... rs6000: Preserve REG_EH_REGION when replacing load/store [P (*)
a5271b1... Daily bump. (*)
789c4b9... c++: aggregate prvalue as for range [PR106230] (*)
a6efab5... Dispatch code for floating point range ops. (*)
838da6c... analyzer: convert tests with dos2unix (*)
9365b2b... analyzer: fix coding style in sm-fd.cc (*)
16aafa3... PR target/91681: zero_extendditi2 pattern for more optimiza (*)
ca1e4b2... [PR middle-end/106432] Gracefully handle unsupported type i (*)
4c6567b... c++: -Woverloaded-virtual false positive [PR87729] (*)
556b816... RTEMS: Do not define _GNU_SOURCE by default (*)
613e3b8... middle-end/106414 - fix mistake in ~(x ^ y) -> x == y patte (*)
eb966d3... aarch64: Implement ACLE Data Intrinsics (*)
(*) This commit already exists in another branch.
Because the reference `refs/heads/devel/sphinx' matches
your hooks.email-new-commits-only configuration,
no separate email is sent for this commit.
next reply other threads:[~2022-07-26 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 8:04 Martin Liska [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-07 13:38 Martin Liska
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=20220726080413.98C5B3858CDA@sourceware.org \
--to=marxin@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).