Re: [PATCH 5/7] gcov: add gcov profiling infrastructure

[Ralf Baechle]

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@xxxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/