public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jiu Fu Guo <guojiufu@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/guojiufu/heads/personal-branch] Daily bump.
Date: Fri, 22 May 2020 06:54:18 +0000 (GMT) [thread overview]
Message-ID: <20200522065418.EABD0386F023@sourceware.org> (raw)
The branch 'guojiufu/heads/personal-branch' was updated to point to:
03d549090e3... Daily bump.
It previously pointed to:
a213f0c096c... Do not turn on -fcomplete-unroll-loops implicitly at -O2
Diff:
!!! WARNING: THE FOLLOWING COMMITS ARE NO LONGER ACCESSIBLE (LOST):
-------------------------------------------------------------------
a213f0c... Do not turn on -fcomplete-unroll-loops implicitly at -O2
772bfd1... seperate -fcomplete-unroll-loops
commit a213f0c096cd8ce62def861df6d98fd58f1ff0e8
Author: Jiufu Guo <guojiufu@linux.ibm.com>
Date: Fri May 22 14:35:01 2020 +0800
Do not turn on -fcomplete-unroll-loops implicitly at -O2
commit 772bfd170e683798ab4b65f5c6ef2eab7a03bf6f
Author: Jiufu Guo <guojiufu@linux.ibm.com>
Date: Fri May 22 14:28:17 2020 +0800
seperate -fcomplete-unroll-loops
next reply other threads:[~2020-05-22 6:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 6:54 Jiu Fu Guo [this message]
2020-06-10 2:54 Jiu Fu Guo
2020-07-08 9:10 Jiu Fu Guo
2020-07-08 9:15 Jiu Fu Guo
2021-05-31 6:02 Jiu Fu Guo
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=20200522065418.EABD0386F023@sourceware.org \
--to=guojiufu@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).