LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh@linux01.gwdg.de>
To: Ian Molton <spyro@f2s.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Stephen Hemminger <shemminger@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] udivdi3: 64 bit divide
Date: Wed, 28 Feb 2007 23:30:13 +0100 (MET) [thread overview]
Message-ID: <Pine.LNX.4.61.0702282327410.23355@yvahk01.tjqt.qr> (raw)
In-Reply-To: <45E4B33D.8080705@f2s.com>
On Feb 27 2007 22:39, Ian Molton wrote:
> Russell King wrote:
>> On Tue, Feb 27, 2007 at 01:36:56PM -0800, Andrew Morton wrote:
>> > On Tue, 27 Feb 2007 13:18:40 -0800 Stephen Hemminger
>> > <shemminger@linux-foundation.org> wrote:
>> > > Then we should pull the existing udivdi3 implementations?
>> > >
>> > Not much point really. Some architectures have gone
>> > and done that, but x86 has not. x86 has enough
>> > coverage for us to pick up most problems, and any
>> > remaining problems are obviously in scruffy
>> > architectures which don't care about performance ;)
>>
>> I doubt arm26 uses udivdi3, but that's something Ian
>> would have to confirm.
>
> I doubt it is used also, however I am not in a position
> to test this until at least after I have moved house.
> Please leave alone for now.
Simple. The non-arch specific code does not use 64/64
divides through the "/" operator (otherwise there would
already have been udivdi3 linking errors). So what
remains to check is arch/arm26. grep -Pr 'int64|\bu64'
returns only a few results to check (kernel/ecard.c,
nwfpe/), so the answer is most likely no.
Jan
--
next prev parent reply other threads:[~2007-02-28 22:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 1:35 Stephen Hemminger
2007-02-27 20:24 ` Andrew Morton
2007-02-27 21:18 ` Stephen Hemminger
2007-02-27 21:36 ` Andrew Morton
2007-02-27 22:24 ` Russell King
2007-02-27 22:39 ` Ian Molton
2007-02-28 22:30 ` Jan Engelhardt [this message]
2007-03-01 17:02 ` Ian Molton
2007-03-01 1:29 ` Tim Schmielau
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=Pine.LNX.4.61.0702282327410.23355@yvahk01.tjqt.qr \
--to=jengelh@linux01.gwdg.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=spyro@f2s.com \
--subject='Re: [PATCH] udivdi3: 64 bit divide' \
/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
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).