public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: Denis Zaitsev <zzz@cd-club.ru>
Cc: Keith Owens <kaos@ocs.com.au>,
	linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: FIXED_486_STRING ?
Date: Mon, 15 Apr 2002 03:03:55 +0200	[thread overview]
Message-ID: <20020415030355.D20383@suse.de> (raw)
In-Reply-To: <20020413224743.A13355@natasha.zzz.zzz> <32667.1018744038@ocs3.intra.ocs.com.au> <20020414024406.A16692@suse.de> <20020415063825.A2691@natasha.zzz.zzz>

On Mon, Apr 15, 2002 at 06:38:26AM +0600, Denis Zaitsev wrote:
 > Yes, the special code for Pentium is important for it, as that code is
 > faster and shorter.  The last signature in string-486.h is of
 > 2000/05/09, so, if this is true, the problems have not been fixed.
 > So, what is the real situation?  I would like to fix the code, and it
 > seems that I'm not alone :)

Petko Manolov <lz5mj@yahoo.com> did some work on them circa 2.4.0test.
His patch is at http://www.dce.bg/~petkan/linux/string-486.diff
Aparently there are still 1-2 problems with these routines which is
why he hasn't pushed for inclusion I guess.

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2002-04-15  1:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-13 16:47 FIXED_486_STRING ? Denis Zaitsev
2002-04-14  0:27 ` Keith Owens
2002-04-14  0:44   ` Dave Jones
2002-04-15  0:38     ` Denis Zaitsev
2002-04-15  1:03       ` Dave Jones [this message]
2002-04-15  1:25         ` Denis Zaitsev
2002-04-15  1:36           ` Dave Jones
2002-04-15  1:46             ` Denis Zaitsev

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=20020415030355.D20383@suse.de \
    --to=davej@suse.de \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=zzz@cd-club.ru \
    /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