Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: Manuel Lauss <manuel.lauss@googlemail.com>
Cc: Jabir M <Jabir_M@pmc-sierra.com>,
	linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: Re:
Date: Fri, 11 Jun 2010 10:06:50 -0700	[thread overview]
Message-ID: <4C126D2A.6040305@caviumnetworks.com> (raw)
In-Reply-To: <AANLkTimHTt3jCTPrlIDAkdDc8WheBf7bdEThk3JO8yNO@mail.gmail.com>

On 06/11/2010 07:32 AM, Manuel Lauss wrote:
> Hi,
>
> On Fri, Jun 11, 2010 at 4:06 PM, Jabir M<Jabir_M@pmc-sierra.com>  wrote:
>>     I am working on a FPU-less 34k MIPS platform with linux-2.6.24
>> kernel. After running a Darwin media streaming server on the board
>> for a while, my oprofile results shows high utilization on
>> fpu_emulator_cop1Handler()&  r4k_wait().
>>

r4k_wait() is the idle task, so that indicates there is nothing to do at 
those sample points.

>> wiki page http://www.linux-mips.org/wiki/Floating_point says gcc will
>> use hard float as default and soft float is best suited model for a
>> fpu less processor.  Could anyone kindly help me in understanding use
>> of -msoft-float .
>> Whether I need to compile
>>
>> 1. kernel with -msoft-float ? or

The kernel doesn't use floating point.  So it doesn't matter.

>> 2. Glibc ? or
>> 3. Application ? or
>> 4. All the above ?
>

If you don't want to use the kernel's FP emulator, you need 2 and 3.


> I have fought with this in the past; what you need to do is:
> - build gcc with softfloat support (mipsel-softfloat-linux-gnu triplet
> for example),
> - build a libc with this new compiler,
> - then rebuild all libraries and apps with you new softfloat toolchain.
>
> <plug>
> I have a working softfloat environment for MIPS32 here at [1], it includes a
> complete c/c++ toolchain with gcc-4.4.3.   It's built for mips32r1, no idea if
> it is supposed to work with 34k cores.
> </plug>

34k is mips32r2, which will run r1 code with no problem.

>
> Best regards,
>          Manuel Lauss
>
> [1]  http://mlau.at/files/mips32-linux/
>
>

  reply	other threads:[~2010-06-11 17:07 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-11 14:06 Jabir M
2010-06-11 14:06 ` Jabir M
2010-06-11 14:32 ` Manuel Lauss
2010-06-11 17:06   ` David Daney [this message]
2010-06-11 17:33     ` Re: Kevin D. Kissell
2010-06-11 18:28       ` Re: Manuel Lauss
2010-06-23 11:25         ` soft-float Jabir M
2010-06-23 11:25           ` soft-float Jabir M
2010-06-23 15:52           ` soft-float Manuel Lauss
  -- 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
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-16  6:09 Re: Fuxin Zhang
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=4C126D2A.6040305@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=Jabir_M@pmc-sierra.com \
    --cc=linux-mips@linux-mips.org \
    --cc=manuel.lauss@googlemail.com \
    --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