From: Xinliang David Li <davidxl@google.com>
To: Rong Xu <xur@google.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [google gcc-4.9] FDO build for linux kernel
Date: Thu, 13 Nov 2014 20:34:00 -0000 [thread overview]
Message-ID: <CAAkRFZL1OB-RH2yCpBmSE8_0Uqt2toMgUVQO3JifWqwnd0hY7g@mail.gmail.com> (raw)
In-Reply-To: <CAF1bQ=TnZiWoYiy1u42qByv+Zjg+a4k6N4QUp9RYscU=1EpuTA@mail.gmail.com>
ok.
(the way to detect kernel build looks unpolished, but there does not
seem to be a consistent way of doing it. Some targets have kernel
specific flags ..)
On Thu, Nov 13, 2014 at 10:40 AM, Rong Xu <xur@google.com> wrote:
> Here is patch that ports our work on FDO linux kernel build support to
> gcc-4_9. With this patch, kernel will use the libgcov functions to
> dump the gcda files.
>
> This patch also enables LIPO build. But the module grouping is not
> computed online. We will use gcov-tool to do this offline.
>
> Tested with kernel FDO build, regression and google internal benchmarks.
>
> Thanks,
>
> -Rong
prev parent reply other threads:[~2014-11-13 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 18:57 Rong Xu
2014-11-13 20:34 ` Xinliang David Li [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=CAAkRFZL1OB-RH2yCpBmSE8_0Uqt2toMgUVQO3JifWqwnd0hY7g@mail.gmail.com \
--to=davidxl@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=xur@google.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).