From: Nigel Stephens <nigel@mips.com>
To: "Kevin D. Kissell" <kevink@mips.com>, Franck <vagabon.xyz@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [RFC] Optimize swab operations on mips_r2 cpu
Date: Thu, 26 Jan 2006 15:51:28 +0000 [thread overview]
Message-ID: <43D8F000.9010106@mips.com> (raw)
In-Reply-To: <005101c6228c$6ebfb0a0$10eca8c0@grendel>
Kevin D. Kissell wrote:
>Could you please post your mipsel-linux-gcc -v output? It might help.
>I've never tried building Linux with any of the Sc/Sd/SmartMIPS options,
>so I really don't know what you could be experiencing. One thought that
>comes to mind is that the -march=4ksd option may be treated as a hint to
>generate compact code (for smart cards) in a way that -march=mips32r2
>is not. I'll ask around...
>
>
Assuming that this is the SDE compiler, then I think that the only
significant thing which -march=4ksd will do differently from
-march=mips32r2 is to allow the compiler to generate branch-likely
instructions -- they're deprecated for generic mips32 code but carry no
penalty on the 4K core. It will also cause the compiler's "4kc" pipeline
description to be used for instruction scheduling, instead of the
default "24kc", but that should only change the order of instructions
and shouldn't really make a significant difference to the code size.
>
>>Now the size of the kernel code is 33Ko bigger ! I have no idea
>>why...I tried to add -mips16e option but it fails to compile...Do you
>>have an idea ?
>>
>>
>>
You certainly can't compile the kernel with -mips16e: too much inline
asm code which won't work in mips16.
Nigel
next prev parent reply other threads:[~2006-01-26 15:47 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 9:36 [RFC] Optimize swab operations on mips_r2 cpu Franck
2006-01-25 12:47 ` Ralf Baechle
2006-01-25 13:34 ` Franck
2006-01-25 14:11 ` Kevin D. Kissell
2006-01-25 14:14 ` Ralf Baechle
2006-01-25 14:32 ` Franck
2006-01-25 15:04 ` Ralf Baechle
2006-01-25 18:03 ` Franck
2006-01-25 18:15 ` Kevin D. Kissell
2006-01-26 8:11 ` Franck
2006-01-26 8:26 ` Kevin D. Kissell
2006-01-26 8:47 ` Franck
2006-01-26 9:17 ` Kevin D. Kissell
2006-01-26 9:17 ` Kevin D. Kissell
2006-01-26 11:56 ` Franck
2006-01-26 15:02 ` Franck
2006-01-26 15:23 ` Kevin D. Kissell
2006-01-26 15:23 ` Kevin D. Kissell
2006-01-26 15:29 ` Franck
2006-01-26 15:51 ` Nigel Stephens [this message]
2006-01-26 16:31 ` Franck
2006-01-26 16:53 ` Kevin D. Kissell
2006-01-26 16:53 ` Kevin D. Kissell
2006-01-26 16:55 ` Nigel Stephens
2006-01-26 18:02 ` Franck
2006-01-26 20:25 ` Nigel Stephens
2006-01-27 9:03 ` Franck
2006-01-27 10:13 ` Kevin D. Kissell
2006-01-27 10:13 ` Kevin D. Kissell
2006-01-27 10:45 ` Franck
2006-01-27 11:31 ` Ralf Baechle
2006-01-27 12:53 ` Kevin D. Kissell
2006-01-27 12:53 ` Kevin D. Kissell
2006-01-27 14:44 ` Franck
2006-01-27 11:30 ` Ralf Baechle
2006-01-27 13:45 ` Nigel Stephens
2006-01-27 14:54 ` Franck
2006-01-27 15:04 ` Maciej W. Rozycki
2006-01-27 15:39 ` Kevin D. Kissell
2006-01-27 15:39 ` Kevin D. Kissell
2006-01-27 17:32 ` Franck
2006-01-29 15:07 ` Ralf Baechle
2006-01-30 13:08 ` Maciej W. Rozycki
2006-01-30 14:31 ` Franck
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=43D8F000.9010106@mips.com \
--to=nigel@mips.com \
--cc=kevink@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=vagabon.xyz@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.