All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Peter Oberparleiter <peter.oberparleiter@de.ibm.com>
Cc: linux-kernel@vger.kernel.org, ltp-coverage@lists.sourceforge.net,
	Sam Ravnborg <sam@ravnborg.org>,
	Peter Oberparleiter <oberparleiter@googlemail.com>,
	Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH 5/7] gcov: add gcov profiling infrastructure
Date: Fri, 23 May 2008 00:11:36 -0700	[thread overview]
Message-ID: <20080523001136.59ec8b34.akpm@linux-foundation.org> (raw)
In-Reply-To: <48313DE6.30802@de.ibm.com>

On Mon, 19 May 2008 10:44:22 +0200 Peter Oberparleiter <peter.oberparleiter@de.ibm.com> wrote:

> +	Note that a kernel compiled with profiling flags will be significantly
> +        larger and run slower. Also be sure to exclude files from profiling
> +        which are not linked to the kernel image to prevent linker errors.

heh, it was all too much for mips.

{standard input}: Assembler messages:
{standard input}:2716: Error: Branch out of range
{standard input}:2819: Error: Branch out of range
{standard input}:2884: Error: Branch out of range
{standard input}:3032: Error: Branch out of range
{standard input}:3097: Error: Branch out of range
{standard input}:3151: Error: Branch out of range
{standard input}:3216: Error: Branch out of range
make[1]: *** [drivers/telephony/ixj.o] Error 1
make: *** [drivers/telephony/ixj.o] Error 2

  reply	other threads:[~2008-05-23  7:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19  8:44 [PATCH 5/7] gcov: add gcov profiling infrastructure Peter Oberparleiter
2008-05-23  7:11 ` Andrew Morton [this message]
2008-05-23  8:45   ` Ralf Baechle
2008-05-27  8:41     ` Peter Oberparleiter
2008-06-02 11:52     ` Marian Jancar
2008-07-02 11:24       ` Ralf Baechle
2008-05-23  9:29 ` Arnd Bergmann

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=20080523001136.59ec8b34.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltp-coverage@lists.sourceforge.net \
    --cc=oberparleiter@googlemail.com \
    --cc=peter.oberparleiter@de.ibm.com \
    --cc=ralf@linux-mips.org \
    --cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.