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, 17 Oct 2022 08:20:08 +0000 (GMT) [thread overview]
Message-ID: <20221017082008.4ED9C3858D3C@sourceware.org> (raw)
The branch 'devel/sphinx' was updated to point to:
6c22519f332... Merge branch 'master' into devel/sphinx
It previously pointed to:
2c92cfe87d2... Merge branch 'master' into devel/sphinx
Diff:
Summary of changes (added commits):
-----------------------------------
6c22519... Merge branch 'master' into devel/sphinx
f10b9f6... elf: ELF toolchain --without-{headers, newlib} should provi (*)
fd206f0... Initial Meteorlake Support (*)
470a065... Initial Raptorlake Support (*)
aedf7eb... Daily bump. (*)
6366e3e... Add new constraints for upcoming autoinc fixes (*)
709b216... Rename "z" constraint to "Zz" on the H8/300 (*)
6c3da5c... Fix bug in register move costing on H8/300 (*)
8f605de... Daily bump. (*)
030a08c... libstdc++: Fix -Wunused-function warning in src/c++11/debug (*)
378a0f1... libstdc++: Implement constexpr std::to_chars for C++23 (P22 (*)
e24b430... libstdc++: Fix uses_allocator_construction args for cv pair (*)
(*) 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-10-17 8:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 8:20 Martin Liska [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-03 19:33 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=20221017082008.4ED9C3858D3C@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).