From: Jeff Law <jeffreyalaw@gmail.com>
To: juzhe.zhong@rivai.ai, gcc-patches@gcc.gnu.org
Cc: kito.cheng@gmail.com, palmer@dabbelt.com
Subject: Re: [PATCH] RISC-V: Fix incorrect annotation
Date: Mon, 19 Dec 2022 17:28:34 -0700 [thread overview]
Message-ID: <f46374ac-ab87-dba1-ddce-d108c283f412@gmail.com> (raw)
In-Reply-To: <20221219231354.135626-1-juzhe.zhong@rivai.ai>
On 12/19/22 16:13, juzhe.zhong@rivai.ai wrote:
> From: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-vsetvl.cc (anticipatable_occurrence_p): Fix incorrect annotations.
> (available_occurrence_p): Ditto.
> (backward_propagate_worthwhile_p): Ditto.
> (can_backward_propagate_p): Ditto.
OK. And more generally, fixes like this don't need review. Consider
them pre-approved for the future.
jeff
next prev parent reply other threads:[~2022-12-20 0:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 23:13 juzhe.zhong
2022-12-20 0:28 ` Jeff Law [this message]
[not found] ` <36D1C05330B9612D+065D340F-26F5-4844-8ACE-EA8091A41E6A@rivai.ai>
2022-12-20 16:02 ` Jeff Law
2022-12-20 16:06 ` Palmer Dabbelt
2022-12-20 16:15 ` Jeff Law
2022-12-20 23:33 ` 钟居哲
2022-12-20 23:38 ` Palmer Dabbelt
2022-12-23 5:47 ` Kito Cheng
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=f46374ac-ab87-dba1-ddce-d108c283f412@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.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).