public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/aoliva/heads/testme] (3 commits) turn -finline-memset-loops into -finline-stringops
Date: Fri, 20 Jan 2023 18:50:07 +0000 (GMT) [thread overview]
Message-ID: <20230120185007.2AC873858D20@sourceware.org> (raw)
The branch 'aoliva/heads/testme' was updated to point to:
cd0f06c2184... turn -finline-memset-loops into -finline-stringops
It previously pointed to:
601dfcd7476... turn -finline-memset-loops into -finline-stringops
Diff:
!!! WARNING: THE FOLLOWING COMMITS ARE NO LONGER ACCESSIBLE (LOST):
-------------------------------------------------------------------
601dfcd... turn -finline-memset-loops into -finline-stringops
938f55f... Introduce -finline-all-stringops=memset
Summary of changes (added commits):
-----------------------------------
cd0f06c... turn -finline-memset-loops into -finline-stringops
9201ad5... Introduce -finline-all-stringops=memset
43ad467... [docs] note that -g opts are implicitly negatable too
reply other threads:[~2023-01-20 18: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=20230120185007.2AC873858D20@sourceware.org \
--to=aoliva@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).