From: Ralf Baechle <ralf@linux-mips.org>
To: Franck <vagabon.xyz@gmail.com>
Cc: "Kevin D. Kissell" <kevink@mips.com>,
Nigel Stephens <nigel@mips.com>,
linux-mips@linux-mips.org
Subject: Re: [RFC] Optimize swab operations on mips_r2 cpu
Date: Sun, 29 Jan 2006 15:07:48 +0000 [thread overview]
Message-ID: <20060129150747.GC3420@linux-mips.org> (raw)
In-Reply-To: <cda58cb80601270932x323e4923j@mail.gmail.com>
On Fri, Jan 27, 2006 at 06:32:15PM +0100, Franck wrote:
> > ifdef CONFIG_CPU_SMARTMIPS
> > cflags-$(CONFIG_CPU_MIPS32R1) += \
> > $(call set_gccflags,mips32,smartmips,4kec,mips3,mips2)\
> > -Os, -Wa,--trap
-Os has no business here. That's what CONFIG_CC_OPTIMIZE_FOR_SIZE is for.
> > if the values I threw in for the MIPS32R1+SmartMIPS (e.g. 4KSc) combination
> > would actually work. I just want to point out that it isn't that hard to do.
>
> I agree it's not hard to do. But it becomes more tricky if you want
> something clean that gives best results for every cpus...Moreover I
> don't think your solution avoids maintenence problems IMHO.
>
> Ralf, could you give your opinion ?
I think I'm going to start by throwing the insane option selection
complexity which was needed for support of gcc 2.95 ... 3.1; a few days
gcc 3.2 became the minimum required to build a 2.6 kernel, then see what
can nicely be implemented.
Ralf
next prev parent reply other threads:[~2006-01-30 13:01 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
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 [this message]
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=20060129150747.GC3420@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=kevink@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=nigel@mips.com \
--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.