From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Kewen.Lin" <linkw@linux.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Jan Hubicka <hubicka@ucw.cz>,
Richard Biener <richard.guenther@gmail.com>,
Richard Sandiford <richard.sandiford@arm.com>
Subject: Re: [PATCH] predict: Adjust optimize_function_for_size_p [PR105818]
Date: Tue, 14 Jun 2022 07:53:17 -0500 [thread overview]
Message-ID: <20220614125317.GY25951@gate.crashing.org> (raw)
In-Reply-To: <23b4998b-bbe6-b052-d7f5-5304ee0f46a3@linux.ibm.com>
On Tue, Jun 14, 2022 at 03:57:08PM +0800, Kewen.Lin wrote:
> PR target/105818
Change this to something else? It is not a target bug. "middle-end"
perhaps?
Thanks for fixing this,
Segher
next prev parent reply other threads:[~2022-06-14 12:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 7:57 Kewen.Lin
2022-06-14 11:37 ` Jan Hubicka
2022-06-15 6:20 ` Kewen.Lin
2022-07-11 3:42 ` Kewen.Lin
2022-08-15 8:33 ` Kewen.Lin
2022-08-29 6:35 ` Kewen.Lin
2022-09-28 5:46 ` Kewen.Lin
2022-06-14 12:53 ` Segher Boessenkool [this message]
2022-06-15 6:21 ` Kewen.Lin
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=20220614125317.GY25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=linkw@linux.ibm.com \
--cc=richard.guenther@gmail.com \
--cc=richard.sandiford@arm.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).