From: Peter Bergner <bergner@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Michael Meissner <meissner@linux.ibm.com>,
gcc-patches@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>,
Will Schmidt <will_schmidt@vnet.ibm.com>
Subject: Re: Ping #5: [PATCH, V4] Eliminate power8 fusion options, use power8 tuning, PR target/102059
Date: Thu, 5 May 2022 16:35:57 -0500 [thread overview]
Message-ID: <45551814-9aa3-a832-a888-e694104db627@linux.ibm.com> (raw)
In-Reply-To: <20220505212733.GH25951@gate.crashing.org>
On 5/5/22 4:27 PM, Segher Boessenkool wrote:
> On Thu, May 05, 2022 at 02:59:07PM -0500, Peter Bergner wrote:
>> On 5/5/22 2:35 PM, Segher Boessenkool wrote:
>>> A patch like that is pre-approved, even for trunk.
>>
>> That works for me! I will apply this directly to GCC 10 and regtest and
>> push if clean so we can unblock our customer.
>>
>> As for trunk, GCC 12 & 11, I think we can wait for the backport of Mike's
>> patch that removes the option altogether.
>
> Please put it on trunk and 12 and 11 as well. To keep things sane.
Will do.
Peter
next prev parent reply other threads:[~2022-05-05 21:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 1:14 Michael Meissner
2022-04-20 16:01 ` Ping: " Michael Meissner
2022-04-20 20:06 ` Peter Bergner
2022-04-20 21:20 ` will schmidt
2022-04-26 16:19 ` Ping: " Michael Meissner
2022-04-28 19:20 ` Ping #4: " Michael Meissner
2022-05-03 1:06 ` Ping #5: " Michael Meissner
2022-05-05 18:59 ` Peter Bergner
2022-05-05 19:35 ` Segher Boessenkool
2022-05-05 19:59 ` Peter Bergner
2022-05-05 21:27 ` Segher Boessenkool
2022-05-05 21:35 ` Peter Bergner [this message]
2022-05-06 16:46 ` Peter Bergner
2022-05-05 22:51 ` Michael Meissner
2022-05-05 22:56 ` Peter Bergner
2022-05-05 19:12 ` Segher Boessenkool
2022-05-05 20:21 ` Michael Meissner
2022-05-05 21:44 ` Segher Boessenkool
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=45551814-9aa3-a832-a888-e694104db627@linux.ibm.com \
--to=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=meissner@linux.ibm.com \
--cc=segher@kernel.crashing.org \
--cc=will_schmidt@vnet.ibm.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).