From: Fuxin Zhang <fxzhang@ict.ac.cn>
To: emblinux@macrohat.com
Cc: linux-cvs <linux-cvs@linux-mips.org>,
linux-mips <linux-mips@linux-mips.org>
Subject: Re:
Date: Tue, 16 Nov 2004 14:09:57 +0800 [thread overview]
Message-ID: <419999B5.3070901@ict.ac.cn> (raw)
Probably because -O3 automatically make short functions inline so
local_sb1___flush_cache_all disappears
asm("sb1___flush_cache_all_ipi = local_sb1___flush_cache_all");
^^^^^^^^^I don't know whether this trick is safe for auto-inlining.
as for the problem of adding prefetch to memcpy, I am not famliar with SB1250,
but as of version 2.4.22, arch/mips/lib/memcpy.S already support using MIPS IV
prefetch
macrohat wrote:
>Dear Fuxin Zhang:
>
>Thinks for your help!
>
>Now i have another question, I use mips-linux-gcc which is ported from gcc-3.2.3 by Broadcom to compile linux kernel,when I use "-O2" or "-Os" option, it can complete successfully, but if i use "-O3" option, it can not complete.Enclosed is the err log and souce code.
>Any help would be really appreciated.
>
>err log:
>
>arch/mips64/mm/mm.o: In function `sb1___flush_cache_all':
>arch/mips64/mm/mm.o(.text+0x1930): undefined reference to `local_sb1___flush_cac
>he_all'
>arch/mips64/mm/mm.o(.text+0x1934): undefined reference to `local_sb1___flush_cac
>he_all'
>make: *** [vmlinux] Error 1
>
>source code:
>
>static void local_sb1___flush_cache_all(void)
>{
> TRACE_RECORD(TRC_CACHEOP_BASE+5, 0, 0,
> read_c0_count());
>
> __sb1_writeback_inv_dcache_all();
> __sb1_flush_icache_all();
>}
>
>extern void sb1___flush_cache_all_ipi(void *ignored);
>asm("sb1___flush_cache_all_ipi = local_sb1___flush_cache_all");
>
>static void sb1___flush_cache_all(void)
>{
> smp_call_function(sb1___flush_cache_all_ipi, 0, 1, 1);
> local_sb1___flush_cache_all();
>}
>
>
>Regards!
>
> macrohat
> emblinux@macrohat.com
> 2004-11-14
>
>
next reply other threads:[~2004-11-16 6:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 6:09 Fuxin Zhang [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-17 9:09 Paulo Miguel Almeida
2024-10-17 9:12 ` Paulo Miguel Almeida
2020-05-06 5:52 Jiaxun Yang
2020-05-06 17:17 ` Nick Desaulniers
2017-11-13 14:55 Re: Amos Kalonzo
2017-11-13 14:55 ` Re: Amos Kalonzo
2017-02-23 15:09 Qin's Yanjun
2017-02-23 15:09 ` RE: Qin's Yanjun
2010-06-11 14:06 Jabir M
2010-06-11 14:32 ` Manuel Lauss
2010-06-11 17:06 ` Re: David Daney
2010-06-11 17:33 ` Re: Kevin D. Kissell
2010-06-11 18:28 ` Re: Manuel Lauss
2006-01-04 12:50 Sathesh Babu Edara
2006-01-04 13:06 ` Kevin D. Kissell
2006-01-09 7:43 ` Sathesh Babu Edara
2006-01-09 7:43 ` RE: Sathesh Babu Edara
2006-01-09 9:00 ` Kevin D. Kissell
2006-01-09 9:00 ` Re: Kevin D. Kissell
2005-04-28 21:30 Raj Palani
2005-04-28 19:15 Bryan Althouse
2005-05-04 13:55 ` Alex Gonzalez
2005-05-04 14:22 ` Bryan Althouse
2005-05-04 14:22 ` RE: Bryan Althouse
2005-05-04 16:42 ` Ralf Baechle
2005-05-05 14:55 ` Re: Ralf Baechle
2005-05-05 15:08 ` Bryan Althouse
2005-05-05 15:08 ` RE: Bryan Althouse
2005-05-05 15:11 ` Ralf Baechle
2005-05-05 15:57 ` Re: Geert Uytterhoeven
2005-05-05 17:13 ` Re: Christoph Hellwig
2004-11-14 1:32 Re: Fuxin Zhang
2004-11-13 14:47 Re: macrohat
2004-09-03 8:57 xuhaoz
2004-09-03 21:47 ` Fuxin Zhang
2004-08-27 1:49 Re: bel racu
2004-04-14 6:05 caoxiang
2004-04-14 18:34 ` Fuxin Zhang
2003-11-01 1:38 Lyle Bainbridge
2003-11-03 18:14 ` Pete Popov
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=419999B5.3070901@ict.ac.cn \
--to=fxzhang@ict.ac.cn \
--cc=emblinux@macrohat.com \
--cc=linux-cvs@linux-mips.org \
--cc=linux-mips@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