All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: Daniel Egger <degger@fhm.edu>,
	Dave Jones <davej@codemonkey.org.uk>,
	Joseph <jospehchan@yahoo.com.tw>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Why does C3 CPU downgrade in kernel 2.4.20?
Date: Thu, 12 Dec 2002 19:09:57 +0100	[thread overview]
Message-ID: <20021212180957.GA184@elf.ucw.cz> (raw)
In-Reply-To: <200212110829.gBB8Tja05013@Port.imtp.ilyichevsk.odessa.ua>

Hi!

> > > I believe someone (Jeff Garzik?) benchmarked gcc code generation,
> > > and the C3 executed code scheduled for a 486 faster than it did for
> > > -m586
> > > I'm not sure about the alignment flags. I've been meaning to look
> > > into that myself...
> >
> > Interesting. I have no clue about which C3 you're talking about here
> > but a VIA Ezra has all 686 instructions including cmov and thus
> > optimising for PPro works best for me.
> >
> > Prolly I would have to do more benchmarking to find out about
> > aligment advantages.
> 
> I heard cmovs are microcoded in Centaurs.
> 
> s...l...o...w...

It still might be faster then a branch... or not if centaurs are
really that simple.
								Pavel
-- 
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?

  parent reply	other threads:[~2002-12-13 11:57 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10  4:02 Why does C3 CPU downgrade in kernel 2.4.20? Joseph
2002-12-10  5:52 ` Dave Jones
2002-12-10  7:22   ` Daniel Egger
2002-12-10  7:24     ` Dave Jones
2002-12-10  7:53       ` Daniel Egger
2002-12-10 12:40     ` Juan Quintela
2002-12-10 15:40       ` Daniel Egger
2002-12-10 16:51     ` Alan Cox
2002-12-10 19:39       ` Daniel Egger
2002-12-10 20:17         ` Jeff Garzik
2002-12-10 21:24         ` Alan Cox
2002-12-11 18:51       ` Bill Davidsen
2002-12-11 19:14         ` Dave Jones
2002-12-11 19:42         ` Jeff Garzik
2002-12-11 19:51           ` Joel Jaeggli
2002-12-12  9:17             ` Joseph
2002-12-12 13:33               ` Dave Jones
2002-12-13  6:55                 ` Joseph
2002-12-13 11:04                   ` Daniel Egger
2002-12-13 11:57                   ` Dave Jones
2002-12-11 21:00         ` Alan Cox
2002-12-12 10:19           ` P
2002-12-11 13:19     ` Denis Vlasenko
2002-12-11 10:58       ` Dave Jones
2002-12-11 19:09         ` Denis Vlasenko
2002-12-11 14:59           ` Dave Jones
2002-12-12 18:09       ` Pavel Machek [this message]
2002-12-14 16:46         ` Denis Vlasenko

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=20021212180957.GA184@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=davej@codemonkey.org.uk \
    --cc=degger@fhm.edu \
    --cc=jospehchan@yahoo.com.tw \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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.