From: Marian Jancar <m.jancar@satca.net>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH 5/7] gcov: add gcov profiling infrastructure
Date: Mon, 02 Jun 2008 13:52:29 +0200 [thread overview]
Message-ID: <4843DEFD.9020303@satca.net> (raw)
In-Reply-To: <20080523084506.GB719@linux-mips.org>
Ralf Baechle wrote:
>> {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.
Please unignore :) It bites when compiling madwifi (without profiling or
anything such).
Marian
next parent reply other threads:[~2008-06-02 12:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48313DE6.30802@de.ibm.com>
[not found] ` <20080523001136.59ec8b34.akpm@linux-foundation.org>
[not found] ` <20080523084506.GB719@linux-mips.org>
2008-06-02 11:52 ` Marian Jancar [this message]
2008-07-02 11:24 ` [PATCH 5/7] gcov: add gcov profiling infrastructure Ralf Baechle
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=4843DEFD.9020303@satca.net \
--to=m.jancar@satca.net \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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