From: Jeff Law <jeffreyalaw@gmail.com>
To: Di Zhao OS <dizhao@os.amperecomputing.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Richard Biener <richard.guenther@gmail.com>
Subject: Re: PING: [PATCH v6] tree-optimization/101186 - extend FRE with "equivalence map" for condition prediction
Date: Tue, 15 Nov 2022 09:00:23 -0700 [thread overview]
Message-ID: <1f72cb1c-6234-e12f-f49d-85d27d1d42d9@gmail.com> (raw)
In-Reply-To: <SN6PR01MB4240C77DD4B2A2E6D013480DE8049@SN6PR01MB4240.prod.exchangelabs.com>
On 11/15/22 03:44, Di Zhao OS via Gcc-patches wrote:
> Hi,
>
> I saw that Stage 1 of GCC 13 development is just ended. So is this
> considered? Or should I bring this up when general development is
> reopened?
Yes, it can still be considered. The guideline is the patch must be
posted before stage1 closes, which this patch obviously was. Richi as
both the release manager and the expert on this part of GCC is by far
the best person to judge the technical aspect of the patch and the
cost/benefit of including it as we work our way through stage3 in our
development cycle.
jeff
prev parent reply other threads:[~2022-11-15 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 0:18 Di Zhao OS
2022-11-15 10:44 ` PING: " Di Zhao OS
2022-11-15 16:00 ` Jeff Law [this message]
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=1f72cb1c-6234-e12f-f49d-85d27d1d42d9@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=dizhao@os.amperecomputing.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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).