public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Peter Oberparleiter <peter.oberparleiter@de.ibm.com>,
	linux-kernel@vger.kernel.org, ltp-coverage@lists.sourceforge.net,
	Sam Ravnborg <sam@ravnborg.org>,
	Peter Oberparleiter <oberparleiter@googlemail.com>
Subject: Re: [PATCH 5/7] gcov: add gcov profiling infrastructure
Date: Fri, 23 May 2008 09:45:07 +0100	[thread overview]
Message-ID: <20080523084506.GB719@linux-mips.org> (raw)
In-Reply-To: <20080523001136.59ec8b34.akpm@linux-foundation.org>

On Fri, May 23, 2008 at 12:11:36AM -0700, Andrew Morton wrote:

> 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

A known problem which I had decieded to ignore until it begins to actually
bite.  It's triggered by something like this

                __asm__ __volatile__(
                "       .set    mips3                                   \n"
                "1:     ll      %0, %1          # atomic_add            \n"
                "       addu    %0, %2                                  \n"
                "       sc      %0, %1                                  \n"
                "       beqz    %0, 2f                                  \n"
                "       .subsection 2                                   \n"
                "2:     b       1b                                      \n"
                "       .previous                                       \n"
                "       .set    mips0                                   \n"
                : "=&r" (temp), "=m" (v->counter)
                : "Ir" (i), "m" (v->counter));

when compiled into a large compilation unit.

  Ralf

  reply	other threads:[~2008-05-23  8:49 UTC|newest]

Thread overview: 5+ 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
2008-05-23  8:45   ` Ralf Baechle [this message]
2008-05-27  8:41     ` Peter Oberparleiter
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=20080523084506.GB719@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox