From: Dehao Chen <dehao@google.com>
To: Xinliang David Li <davidxl@google.com>
Cc: David Edelsohn <dje.gcc@gmail.com>,
Rainer Orth <ro@cebitec.uni-bielefeld.de>,
Jan Hubicka <hubicka@ucw.cz>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] AutoFDO patch for trunk
Date: Wed, 22 Oct 2014 17:24:00 -0000 [thread overview]
Message-ID: <CAO2gOZU0kitSQVQz4=HyOAhZWp9oEJ8=aSMKKxg1Tt+YUBCrrQ@mail.gmail.com> (raw)
In-Reply-To: <CAAkRFZJPyOpR6dQFge2KCQwJJV2QrQWnbTA6wAdWsKO8-iT-aA@mail.gmail.com>
The patch tested OK. And I think it's a trivial patch, and already
committed it to trunk.
About the perf parser. I'm syncing the toolchain to head which should
already have newer kernel support.
Thanks,
Dehao
On Wed, Oct 22, 2014 at 10:07 AM, Xinliang David Li <davidxl@google.com> wrote:
> Can someone pre-approve the patch so that Dehao can check it in after
> basic testing?
>
> David
>
> On Wed, Oct 22, 2014 at 10:06 AM, David Edelsohn <dje.gcc@gmail.com> wrote:
>>>>>>> Rainer Orth writes:
>>
>>> As Joseph is repeating over and over again, *nothing* must be included
>>> before config.h, and auto-profile.c violates this.
>>>
>>> The following patch at least allows the file to compile without errors;
>>> no idea if this the best order for the headers involved.
>>
>>
>> The patch also fixes the problem on AIX.
>>
>>
>> Thanks, David
next prev parent reply other threads:[~2014-10-22 17:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 17:07 David Edelsohn
2014-10-22 17:10 ` Xinliang David Li
2014-10-22 17:24 ` Dehao Chen [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-07 21:24 Dehao Chen
2014-05-07 21:47 ` Xinliang David Li
2014-05-15 21:04 ` Jan Hubicka
2014-10-09 0:24 ` Dehao Chen
2014-10-09 22:34 ` Jan Hubicka
2014-10-10 3:15 ` Dehao Chen
2014-10-14 15:08 ` Jan Hubicka
2014-10-14 21:10 ` Dehao Chen
2014-10-14 23:28 ` Dehao Chen
2014-10-15 2:57 ` Andi Kleen
2014-10-15 14:36 ` Jan Hubicka
2014-10-16 18:57 ` Dehao Chen
2014-10-19 10:02 ` Jan Hubicka
2014-10-20 21:39 ` Dehao Chen
2014-10-21 19:43 ` Markus Trippelsdorf
2014-10-21 21:01 ` Dehao Chen
2014-10-21 21:30 ` Markus Trippelsdorf
2014-10-21 22:32 ` Dehao Chen
2014-10-22 5:58 ` Markus Trippelsdorf
2014-10-22 15:26 ` Rainer Orth
2014-05-16 0:46 ` Jan Hubicka
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='CAO2gOZU0kitSQVQz4=HyOAhZWp9oEJ8=aSMKKxg1Tt+YUBCrrQ@mail.gmail.com' \
--to=dehao@google.com \
--cc=davidxl@google.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=ro@cebitec.uni-bielefeld.de \
/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).