From: Bernd Schmidt <bschmidt@redhat.com>
To: Andi Kleen <andi@firstfloor.org>, gcc-patches@gcc.gnu.org
Subject: Re: [PING^2] Re: Updated autofdo bootstrap and testing patches
Date: Mon, 06 Jun 2016 09:55:00 -0000 [thread overview]
Message-ID: <905a52b6-dc75-5f07-b12e-784840f7c09f@redhat.com> (raw)
In-Reply-To: <87oa7oik55.fsf_-_@tassilo.jf.intel.com>
On 05/30/2016 12:17 AM, Andi Kleen wrote:
> Andi Kleen <andi@firstfloor.org> writes:
>
> Ping^2!
I think patches #1 and #5 had unaddressed comments from Jan. I think you
should ping build system maintainers directly for #4.
Bernd
prev parent reply other threads:[~2016-06-06 9:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-21 16:37 Andi Kleen
2016-05-21 16:37 ` [PATCH 1/5] Add gcc-auto-profile script Andi Kleen
2016-05-21 16:37 ` [PATCH 2/5] Don't cause ICEs when auto profile file is not found with checking Andi Kleen
2016-05-21 16:37 ` [PATCH 3/5] Run profile feedback tests with autofdo Andi Kleen
2016-05-21 16:38 ` [PATCH 4/5] Add make autoprofiledbootstrap Andi Kleen
2016-05-21 16:37 ` [PATCH 5/5] workaround for PR70427 Andi Kleen
2016-05-30 9:16 ` Jan Hubicka
2016-05-30 9:46 ` Andi Kleen
2016-05-21 20:55 ` [PATCH 3/5] Run profile feedback tests with autofdo Bernhard Reutner-Fischer
2016-05-21 21:37 ` Andi Kleen
2016-05-21 20:42 ` [PATCH 2/5] Don't cause ICEs when auto profile file is not found with checking Bernhard Reutner-Fischer
2016-05-30 8:49 ` Jan Hubicka
2016-05-21 18:02 ` [PATCH 1/5] Add gcc-auto-profile script Bernhard Reutner-Fischer
2016-05-30 9:37 ` Jan Hubicka
2016-05-30 9:38 ` Andi Kleen
2016-05-26 17:08 ` [PING] Re: Updated autofdo bootstrap and testing patches Andi Kleen
2016-05-30 8:22 ` [PING^2] " Andi Kleen
2016-06-04 4:12 ` [PING^3] " Andi Kleen
2016-06-06 9:55 ` Bernd Schmidt [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=905a52b6-dc75-5f07-b12e-784840f7c09f@redhat.com \
--to=bschmidt@redhat.com \
--cc=andi@firstfloor.org \
--cc=gcc-patches@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).