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] (12 commits) Merge branch 'master' into devel/sphinx
Date: Mon, 3 Jan 2022 19:33:41 +0000 (GMT) [thread overview]
Message-ID: <20220103193341.8F2B53858C27@sourceware.org> (raw)
The branch 'devel/sphinx' was updated to point to:
013d1573ab1... Merge branch 'master' into devel/sphinx
It previously pointed to:
cb2d70e85a7... Merge branch 'master' into devel/sphinx
Diff:
Summary of changes (added commits):
-----------------------------------
013d157... Merge branch 'master' into devel/sphinx
122a754... c++: Avoid narrowing in make_char_string_pack (*)
4003ecb... Revamp documentation for _Complex types extension (*)
6447f6f... Fortran: Fix array copy-in/copy-out for BIND(C) functions [ (*)
6362627... i386, fab: Optimize __atomic_{add,sub,and,or,xor}_fetch (x, (*)
4911609... middle-end/103851 - ensure SSA names are released during OM (*)
91031bf... symtab: Fold &a == &b to 0 if folding_initializer [PR94716] (*)
814c221... testsuite: fix ASAN errors in i386.exp tests (*)
b043d4f... testsuite: fix vect.exp ASAN errors (*)
c43b590... d: Merge upstream dmd 001bfd97b, druntime 759e6023, phobos (*)
bd5b0fc... docs: Use ; for function declarations. (*)
134442b... c++: Support &typeid(x) == &typeid(y) and typeid(x) == type (*)
(*) 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-01-03 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 19:33 Martin Liska [this message]
2022-10-17 8:20 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=20220103193341.8F2B53858C27@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).