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/marxin/heads/cc-renaming] (14 commits) Manual changes.
Date: Tue, 11 Jan 2022 09:50:11 +0000 (GMT) [thread overview]
Message-ID: <20220111095011.AB4F4389F056@sourceware.org> (raw)
The branch 'marxin/heads/cc-renaming' was updated to point to:
0c0a749b64b... Manual changes.
It previously pointed to:
e649452da16... Manual changes.
Diff:
!!! WARNING: THE FOLLOWING COMMITS ARE NO LONGER ACCESSIBLE (LOST):
-------------------------------------------------------------------
e649452... Manual changes.
a9831f5... Automatic renaming
b9da1f0... Rename files.
Summary of changes (added commits):
-----------------------------------
0c0a749... Manual changes.
32e84f6... Automatic renaming
68a8b77... Rename files.
19d81fd... rs6000: powerpc suboptimal boolean test of contiguous bits (*)
8e86086... State --sysroot option as validated once processed (*)
14cb768... Improve sequence logic in cxx_init_decl_processing (*)
0552605... testsuite: Fix regression on m32 by r12-6087 [PR103820] (*)
2e1116c... rs6000: Remove useless code related to -mno-power10 (*)
4bb79e2... Extend predicate of operands[1] from register_operand to ve (*)
d9450aa... Daily bump. (*)
04a7455... i386: Introduce V2QImode vector compares [PR103861] (*)
ab36b55... c++: constexpr base-to-derived conversion with offset 0 [PR (*)
3e95a97... c++: "more constrained" vs staticness of memfn [PR103783] (*)
54fa7da... c++: Ensure some more that immediate functions aren't gimpl (*)
(*) This commit already exists in another branch.
Because the reference `refs/users/marxin/heads/cc-renaming' matches
your hooks.email-new-commits-only configuration,
no separate email is sent for this commit.
reply other threads:[~2022-01-11 9:50 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=20220111095011.AB4F4389F056@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).