linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Joakim Tjernlund" <Joakim.Tjernlund@lumentis.se>
To: "Tom Rini" <trini@kernel.crashing.org>
Cc: "LinuxPPC" <linuxppc-embedded@lists.linuxppc.org>,
	<alan@lxorguk.ukuu.org.uk>
Subject: Re: ppc_8xx-gcc 2.95.3 Monta Vista does not do ANY loop unrolling
Date: Tue, 12 Nov 2002 22:30:12 +0100	[thread overview]
Message-ID: <001601c28a92$e4a0d8c0$0200a8c0@telia.com> (raw)
In-Reply-To: 20021112184025.GA9033@opus.bloom.county


> On Tue, Nov 12, 2002 at 05:46:49PM +0100, Joakim Tjernlund wrote:
>
> > > > Now to the trick question(s):
> > > > Where might it be suitable to add -funroll-loops or, better yet, can it be done
> > > > with a pragma or attribute attached to the function in question? It's pretty
> > > > hard to unroll inline functions otherwise (and only the inline function).
> > >
> > > Well, to lib/Makefile:
> > > ifeq ($(CONFIG_PPC32),y)
> > > CFLAGS_crc32.o += -funroll-loops
> > > endif
> > >
> > > Should work.  And it's not unheard of.
> >
> > Yes, that much I already figured, but are there OTHER places in
> > the kernel that also might benefit from unrolling. I don't know the
> > kernel as well as you do and was hoping for a lead or two.
>
> Not really.  Unfortunatly what might be better is to figure out how it
> works on i386, and then figure out how to duplicate that logic on PPC,
> maybe making it another flag and then turned on for different sizes
> based on -mtune.

well, according to Mark Hatle it's only gcc 3.3-pre that does this kind of unrolling
automatically so that will take a very long time before it's figured out and usable.

So maybe it's worth the effort  to figure out a few hot spots and apply -funroll-loops there.

-mtune is new to me, need to look that one up.

>
> > > >  Any progress on the i2c-algo-8xx.c and/or 8xx_io/enet.c patches I sent earlier?
> > >
> > > As I said privatly, Dan Malek is handling the enet patch, and I'm
> > > looking for time to do the i2c one.  Right now I'm working on making the
> > > kernel easier to tweak (in some ways) for 2.5.
> >
> > I know Dan is handling the enet stuff, but since you both work
> > for MV(don't you?) I figured you might know, being an insider and all :-)
>
> I don't follow you.  Dan doesn't work for MVista now.

Sorry, I didn't know that.

>
> > Maybe your tweak stuff could make use of forced unrolling?
>
> Eventually, it could be used for turning it on or off for the whole
> kernel, or for a specific area even, once I get Makefile tweaks working.
> First I'm trying to get dependancies right.

makes sense.

    Jocke

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-11-12 21:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-12  8:12 ELDK 2.0, glibc and kernel 2.4.20??? Steven Scholz
2002-11-12  9:40 ` ppc_8xx-gcc 2.95.3 Monta Vista does not do ANY loop unrolling Joakim Tjernlund
2002-11-12 15:22   ` Tom Rini
2002-11-12 16:09     ` Joakim Tjernlund
2002-11-12 16:25       ` Tom Rini
2002-11-12 16:46         ` Joakim Tjernlund
2002-11-12 18:40           ` Tom Rini
2002-11-12 21:30             ` Joakim Tjernlund [this message]
2002-11-12 19:56           ` Mark Hatle
2002-11-12 21:33             ` Joakim Tjernlund
2002-11-12 12:39 ` ELDK 2.0, glibc and kernel 2.4.20??? wolfgang.grandegger
2002-11-12 12:58   ` Steven Scholz
  -- strict thread matches above, loose matches on Subject: below --
2002-11-12  9:56 ppc_8xx-gcc 2.95.3 Monta Vista does not do ANY loop unrolling Jaap-Jan Boor
2002-11-12 10:42 ` Joakim Tjernlund
2002-11-12 10:49 Jaap-Jan Boor
2002-11-12 10:55 ` Joakim Tjernlund

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='001601c28a92$e4a0d8c0$0200a8c0@telia.com' \
    --to=joakim.tjernlund@lumentis.se \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).